Upgrade 5.1.1->5.3.3 can't connect as SYS to db

hi,

We're trying to upgrade one of our databases to 5.3.3 from 5.1.1 but it is not accepting the SYS AS SYSDBA credentials (invalid username/password), however we can access the database with these credentials using sqlplus in the same session. 

It seems to be concatenating the directory of the old version twice as well for some reason so not finding the license file - why is this?

Any ideas?

cheers

Ian & Catherine

snapshot:

uk-abi-sdb21 jchem $ sh ./upgrade-evol.sh
+ /usr/java/jdk1.6.0_11/bin/java -classpath ../lib/jchem.jar:/apps/oracle/product/10.2.0/jdbc/lib/ojdbc5.jar:/apps/oracle/product/10.2.0/jdbc/lib/ojdbc14.jar -Djava.util.logging.config.file=conf/logging.properties chemaxon.jchem.cartridge.install.UpgradeCmdLine --oracle-home /apps/oracle/product/10.2.0


The path to the home directory of the old JChem version: /apps/chemaxon/jchem/5.1.1


====> The directory /apps/chemaxon/jchem/5.1.1/cartridge/apps/chemaxon/jchem/5.1.1/cartridge/licenses, where the old JChem Cartridge version expected the licenses files, doesn't exist.


Name of the Oracle host. [localhost]:


Oracle listener port [1521]:


Name of the Oracle instance [ccddev]:


DBA login [SYSTEM]: SYS AS SYSDBA
DBA password:


====> Error: ORA-01017: invalid username/password; logon denied



DBA login [SYS AS SYSDBA]: + set +x
uk-abi-sdb21 jchem $ sqlplus


SQL*Plus: Release 10.2.0.3.0 - Production on Tue Jun 8 11:56:50 2010


Copyright (c) 1982, 2006, Oracle.  All Rights Reserved.


Enter user-name: SYS AS SYSDBA
Enter password:


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options


SQL>

 

Hi Ian & Catherine,

Regarding the ORA-01017 problem:

Can you successfully connect with SYS AS SYSDBA using SQL*Plus, if you specify the connect string on the command line like this:

sqlplus @localhost:1521/ccddev

?

Regarding the license path problem:

Is the license.dir property in /apps/chemaxon/jchem/5.1.1/conf/jcart.properties file set? If it is, to what value is it set?

Thanks

Peter

Hi Peter,

Yes using sqlplus works fine:

uk-abi-sdb21 jchem $ sqlplus localhost:1521/ccddev 
SQL*Plus: Release 10.2.0.3.0 - Production on Tue Jun 8 14:30:35 2010 
Copyright (c) 1982, 2006, Oracle.  All Rights Reserved. 
ERROR:
ORA-01017: invalid username/password; logon denied 

Enter user-name: sys as sysdba
Enter password: 
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options 
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
uk-abi-sdb21 jchem $ sqlplus sys as sysdba@localhost:1521/ccddev 
SQL*Plus: Release 10.2.0.3.0 - Production on Tue Jun 8 14:31:51 2010 
Copyright (c) 1982, 2006, Oracle.  All Rights Reserved. 
Enter password: 
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options 
SQL> 

license path is set to:

license.dir = /apps/chemaxon/jchem/5.1.1/cartridge/licenses/

which is where the license is installed.

 

As you can tell we're trying to lots of upgrades today!

Many thanks Ian & Catherine

Ian & Catherine,

The license directory path problem is an easy one: removing the trailing slash should solve the problem. This little nuisance will be eliminated in the next minor JChem version.

I am not sure what to make of the SYS login problem. (Upgrading JCC using SYS AS SYSDBA works in my test environment.) Can you make the same connection with other Java tools -- with JChem Manager for example? Unlikely, but who knows: perhaps there is some "special" character in the password which is handled differently when parsed by the upgrade script?

Possible work arounds:

Can you execute the upgrade using SYSTEM? (AFAIK, system is less privileged than SYS AS SYSDBA anyway.) You can also execute the upgrade without DBA account, you'll have to upgrade the indexes "manually" (using the upgradeOnly=y parameter).

Regards,

Peter

Removing the trailing slash from the license directory path results in:

The path to the home directory of the old JChem version: /apps/chemaxon/jchem/5.1.1

====> /apps/chemaxon/jchem/5.1.1/cartridge/licenses for licenses appears to be an absolute path. Nothing to do there.

With the SYS problem - I am starting to wonder if the db is set up ok as when I try and login from toad on a different machine with SYS AS SYSDBA I get insufficient privileges error (ORA-01031). will keep investigating!

many thanks

Ian

 

Removing the trailing slash from the license directory path results in:

This is what is expected. It is assumed that license.dir is specified only, if the default is not suitable for some reason. It is further assumed that an absolute path will be specified, if the license file is shared by multiple applications or hosts. In the latter case, the license files are not supposed to be processed during upgrade.

Regards,

Peter

Hi Peter,

Turns out this was mostly due to a problem with the db set up - upgrade now sorted and working! (now to do test and live!)

regards Ian

Hi Ian,

JChem 5.3.6 has been released -- with the JChem Cartridge upgrade program made insensitive to the trailing slash at the end of the license directory path.

Best regards,

Peter