Quantcast
Viewing latest article 19
Browse Latest Browse All 100

prim37078:”Cannot Log into XXXXXXXX, click here to choose another database”; Populategroups fails with “ORA-00917: missing comma” error in log.

Solution ID: prim37078
"Cannot Log into XXXXXXXX, click here to choose another database"; Populategroups fails with "ORA-00917: missing comma" error in log.
Status: Reviewed
Version(s): 10.0, 10.1, 9.0, 9.1



Fact: Database: Oracle
Problem:

Users can log in to Expedition Administration, but receive error when logging in to Expedition.


“Cannot Log into EXPDB, click here to choose another database”

Problem: Populategroups utility fails with ORA-00917: missing comma error
Problem: Cannot log in to project database
Problem: group_info table is blank
To check for this, log into the oracle instance as expadmin user and run the following SQL query:
select * from group_info;
 
Note: “no rows selected” implies that this table is blank.
Problem: DBSourceCreation.log file on the webserver machine contains errors as below:

Begin
#
java.sql.SQLException: ORA-00917: missing comma

    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:862)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1839)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1764)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2354)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:858)
    at com.primavera.exponline.install.PopulateGroups.writeGroupInfo(PopulateGroups.java:675)
    at com.primavera.exponline.install.PopulateGroups.doPopulate(PopulateGroups.java:321)
    at com.primavera.exponline.install.PopulateGroups.<init>(PopulateGroups.java:167)
    at com.primavera.exponline.install.PopulateGroups.main(PopulateGroups.java:136)
#
java.sql.SQLException: ORA-00917: missing comma

    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:862)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1839)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1764)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2354)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:858)
    at com.primavera.exponline.install.PopulateGroups.writeGroupInfo(PopulateGroups.java:675)
    at com.primavera.exponline.install.PopulateGroups.doPopulate(PopulateGroups.java:321)
    at com.primavera.exponline.install.PopulateGroups.<init>(PopulateGroups.java:167)
    at com.primavera.exponline.install.PopulateGroups.main(PopulateGroups.java:136)
End

Cause: Database password contains a dollar sign ($).  The dollar sign is used to indicate a replacement variable by the PopulateGroups utility.  Using a dollar sign in a password results in an incorrect substitution and thus an invalid data source.
Fix:

  1. Change database password to remove any/all dollar signs

  2. Restart database service

  3. Run server configuration from the webserver machine, specifying the new password defined in step 1 

  4. Ensure, on the final screen of server configuration, “set database connection” and “restart webserver” checkboxes are checked.

  5. After the web server has been restarted, users should be able to login into project database without problems

Viewing latest article 19
Browse Latest Browse All 100

Trending Articles