Comments for idError

Comment on ORA-02185 a token other than WORK follows COMMIT by Balwant rajput

Balwant rajput — Fri, 10 Jun 2011 15:06:54 +0000

Solution: ORA-02185 a token other than WORK follows COMMIT

check your code and see if you add (:) colon instead of ( ; ) semicolon after the COMMIT in your code.

Cheers,
Balwant

Comment on BEA-010026 – Exception occurred during commit of transaction transaction: stackTrace. by Madhan

Madhan — Mon, 02 May 2011 02:54:16 +0000

It is a misconfiguration in the environment – we had used a read-only database user for the EJB, but you are trying to do updates. Strange error given by weblogic in this case, your application code seemed to complete successfully, and then a transaction commit error similar to the above occurred in the server logs.

Comment on Error 1067: The process terminated unexpectedly. by pratik

pratik — Fri, 28 Jan 2011 12:11:20 +0000

The problem is because of tomcat cant find the java installation folder. for that you have to simply follow the steps ,

1) click on the tomcat installation setup.
2)click next until you get the dialogue box :: please select the path of a java SE6.0 or later JRE installed on your system.
3)if there is any predefine path then remove it and give there the path of your java installation folder. if you do not have jre then install it. the path will be something like this(C:\Program Files\Java\jdk1.6.0_18) or (C:\Program Files\Java\jre6) select any of the two. if one cant solve the problem then try with the other one.
4) and just try to start up your server now. it will most probably work..
enjoy..

Comment on BEA-011055 – Error deploying the EJB ‘ejb‘, the JNDI name ‘jndiName‘ is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed. by Nicolas Pignier

Nicolas Pignier — Fri, 19 Nov 2010 13:38:53 +0000

do you have the parameter “upload=true” in your ant target ?

is the ear already deployed by autodeploy ? in this case il will not work with the wldeployer, try overwrite you ear file in the autodeploy directory.

Comment on Error: 1255 – SQLSTATE: HY000 ER_SLAVE_WAS_NOT_RUNNING by admin

admin — Thu, 07 May 2009 00:45:49 +0000

There are cases when slave threads have successfully started and then later stop, because of inability to connect to the master or read binary logs, etc. In such cases, you will not be given a warning that it has stopped. You may add an UNTIL clause to specify that the slave should start and run until the SQL thread
reaches a given point.

Comment on Error: 1253 – SQLSTATE: 42000 ER_COLLATION_CHARSET_MISMATCH by admin

admin — Thu, 07 May 2009 00:45:29 +0000

This error occurs when you try to use a collation that is not supported for a particular character set. Each character set defines it own collations. Example as follows:
COLLATION ‘utf8_bin’ is not valid for CHARACTER SET ‘binary’
Collation ‘utf8_bin’ is available for character set ‘utf8′ and not for ‘binary’.
Check your database, table and column DDL for setting the CHARSET. Note that it can be set on the database level, the table level and the
column level.

Comment on Error: 1252 – SQLSTATE: 42000 ER_SPATIAL_CANT_HAVE_NULL by admin

admin — Thu, 07 May 2009 00:45:13 +0000

Spatial indexes are created using SPATIAL INDEX statement and are available only for MyISAM tables. Index columns must be NOT NULL and column prefix lenghts are not allowed (in MySQL 5.1). See Spatial Extensions for details at http://dev.mysql.com/doc/refman/5.1/en/spatial-extensions.html.

Comment on Error: 1248 – SQLSTATE: 42000 ER_DERIVED_MUST_HAVE_ALIAS by admin

admin — Thu, 07 May 2009 00:44:53 +0000

Add an alias for each derived table and make sure that you add the alias just after the FROM clause, outside the parentheses () and make sure to use JOIN condition as necessary.

Comment on Error: 1243 – SQLSTATE: HY000 ER_UNKNOWN_STMT_HANDLER by admin

admin — Thu, 07 May 2009 00:44:27 +0000

The following are some instances of this error:
Unknown prepared statement handler (prepared_stmt) given to DEALLOCATE
Unknown prepared statement handler (prepared_stmt) given to EXECUTE
Prepared statements are local to the session. MySQL automatically deallocates these statements when the session is closed. For a detailed workaround, follow these steps:
1. Open a database connection
2. Run the PREPARE statement
3. Set the values of the variable and EXECUTE the query
5. DEALLOCATE the prepared statement
6. Close the database connection

Comment on Error: 1242 – SQLSTATE: 21000 ER_SUBQUERY_NO_1_ROW by admin

admin — Thu, 07 May 2009 00:44:11 +0000

This error occurs for statements having a subquery. Check this example:
SELECT * FROM table1 WHERE column1 = (SELECT column1 FROM table2);
If the subquery in the abover statement returns more than 1 row, an error will be triggered. To fix, you may rewrite the query as follows:
SELECT * FROM table1 WHERE column1 = ANY (SELECT column1 FROM table2);