Subscribe
Accepted Solution

SMO 32-bit error on 64-bit system

[ Edited ]

All,

I’m getting:

--[ERROR] SMO-13032: Cannot perform operation: Backup Create.  Root cause: java.rmi.ServerError: Error occurred in server thread; nested exception is:

            java.lang.UnsatisfiedLinkError: /oracle_software/ora11i/product/11.2.0/dbhome_1/lib/libocijdbc11.so: Can't load Sparc v9 64-bit .so on a Sparc 32-bit platform

Which appears to be related to burt 390022: http://web.netapp.com/~burt/views/390/390022.html

Are there any work arounds?  Why is SMO running 32-bit libraries in a 64-bit only environment?

-Neil

Re: SMO 32-bit error on 64-bit system

Neil,

I ran into something very similar recently with a linux installation.  It wasn't SMO, it was Oracle and the way it was linked after installation.  I had to find the correct c-compiler and then relink Oracle.

Craig

Re: SMO 32-bit error on 64-bit system

I switched from O/S to Database Authentication, and the Snapshot succeeded.

Now, cloning fails while starting the cloned database:

--[ INFO] SMO-13046: Operation GUID 8aba8970266c588501266c589c5d0001 starting on Profile DB11GR2
--[ INFO] SMO-04137: Auto-generated label "clone_db11gr2_20100126153531EST" for clone.
--[ INFO] SMO-04030: Validating uniqueness of new SID "cln1".
--[ INFO] SMO-04040: Using ORACLE_HOME of "/oracle_software/ora11i/product/11.2.0/dbhome_1" from clonespec for clone.
--[ INFO] SMO-04042: Using Oracle OS account "ora11i" from clonespec for clone.
--[ INFO] SMO-04044: Using Oracle OS group "dba11i" from clonespec for clone.
--[ INFO] SMO-07127: Locked database for SnapManager operations - created lock file "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/.sm_lock_cln1" on host SUN240.
--[ INFO] SD-00025: Beginning to connect filesystem(s) [/u01] from snapshot smo_db11gr2_db11gr2_f_h_1_8aba8970266c4cf201266c4d02390001_0.
--[ INFO] SD-00016: Discovering storage resources for /u01_CLN1.
--[ INFO] SD-00017: Finished storage discovery for /u01_CLN1.
--[ INFO] SD-00026: Finished connecting filesystem(s) [/u01] from snapshot smo_db11gr2_db11gr2_f_h_1_8aba8970266c4cf201266c4d02390001_0.
--[ INFO] SD-00025: Beginning to connect filesystem(s) [/u03] from snapshot smo_db11gr2_db11gr2_f_h_2_8aba8970266c4cf201266c4d02390001_0.
--[ INFO] SD-00016: Discovering storage resources for /opt/NTAPsmo/mnt/-u03-20100126153557368_0.
--[ INFO] SD-00017: Finished storage discovery for /opt/NTAPsmo/mnt/-u03-20100126153557368_0.
--[ INFO] SD-00026: Finished connecting filesystem(s) [/u03] from snapshot smo_db11gr2_db11gr2_f_h_2_8aba8970266c4cf201266c4d02390001_0.
--[ INFO] ORACLE-00502: Adding entry for database cln1 in /var/opt/oracle/oratab.
--[ INFO] SMO-07300: Beginning clone of database "DB11GR2" to SID "cln1" on host "sun240".
--[ INFO] SMO-07302: Generating parameter file for "cln1" at "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/initcln1.ora".
--[ INFO] SMO-07303: Generating password file for "cln1" at "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/orapwcln1".
--[ INFO] SMO-07304: Starting up database "cln1" in NOMOUNT mode.
--[ INFO] SMO-07305: Generating control files for database "cln1".
--[ INFO] SMO-07312: Create Control File - Database: cln1.
--[ INFO] SMO-07313: Create Control File - Redolog: /u01_CLN1/redo_1.log.
--[ INFO] SMO-07313: Create Control File - Redolog: /u01_CLN1/redo_2.log.
--[ INFO] SMO-07313: Create Control File - Redolog: /u01_CLN1/redo_3.log.
--[ INFO] SMO-07314: Create Control File - Datafile: /u01_CLN1/db11gr2/data/example01.dbf.
--[ INFO] SMO-07314: Create Control File - Datafile: /u01_CLN1/db11gr2/data/users01.dbf.
--[ INFO] SMO-07314: Create Control File - Datafile: /u01_CLN1/db11gr2/data/sysaux01.dbf.
--[ INFO] SMO-07314: Create Control File - Datafile: /u01_CLN1/db11gr2/data/system01.dbf.
--[ INFO] SMO-07314: Create Control File - Datafile: /u01_CLN1/db11gr2/data/undotbs01.dbf.
--[ INFO] SMO-07337: Recovering database clone "cln1" to a consistent point using archived logs from the backup.
--[ERROR] SMO-13032: Cannot perform operation: Clone Create.  Root cause: java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.UnsatisfiedLinkError: /oracle_software/ora11i/product/11.2.0/dbhome_1/lib/libocijdbc11.so: Can't load Sparc v9 64-bit .so on a Sparc 32-bit platform
--[ INFO] SMO-07316: Shutting down database "cln1".
--[ INFO] SMO-07317: Deleting file "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/initcln1.ora".
--[ INFO] SMO-07317: Deleting file "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/orapwcln1".
--[ INFO] SMO-07317: Deleting file "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/hc_cln1.dat".
--[ INFO] SMO-07317: Deleting file "/u01_CLN1/control01.ctl".
--[ INFO] ORACLE-00503: Removing entry for database cln1 from /var/opt/oracle/oratab.
--[ INFO] SD-00031: Beginning to disconnect filesystem(s) [/opt/NTAPsmo/mnt/-u03-20100126153557368_0].
--[ INFO] SD-00032: Finished disconnecting filesystem(s) [/opt/NTAPsmo/mnt/-u03-20100126153557368_0].
--[ INFO] SD-00031: Beginning to disconnect filesystem(s) [/u01_CLN1].
--[ INFO] SD-00032: Finished disconnecting filesystem(s) [/u01_CLN1].
--[ INFO] SMO-07131: Unlocked database for SnapManager operations - removed lock file "/oracle_software/ora11i/product/11.2.0/dbhome_1/dbs/.sm_lock_cln1" on host SUN240.
--[ INFO] SMO-13039: Successfully aborted operation: Clone Create
--[ERROR] SMO-13048: Clone Create Operation Status: FAILED
--[ INFO] SMO-13049: Elapsed Time: 0:01:31.794

-Neil

Re: SMO 32-bit error on 64-bit system

Hi Neil,

Good Day.

11gr2 on Solaris SPARC is still NOT yet supported with SMO 3.0.3.

In SMO we have a reference to lib32 and from Oracle 11g R2 onwards Oracle releases binaries for 64 Bit.

Thanks and Regards,

Viswanathan Balaji.

Re: SMO 32-bit error on 64-bit system

It turns out that Linux is the only 11gr2 platform supported by SMO....

-Neil

Re: SMO 32-bit error on 64-bit system

Hi Guys,

I have something similar but in my case I get these:

--[ERROR] SMO-13032: Cannot perform operation: Clone Create.  Root cause: ORACLE-00001: Error executing SQL: [].  The command returned: SP2-1503: Unable to initialize Oracle call interface

I know these errors I caused by the LD_LIBRARY_PATH and it looks like when smo execute it does a setup of the environment variables.

Is smo using oraenv to setup the environment variables?

Thanks

Re: SMO 32-bit error on 64-bit system

Hello Phuti,

Are you trying to clone the database on the same or an alternate host ?

If you are trying on an alternate host can you make sure:

1. Architecture and OS ( and version) are same on both the hosts.

2. Same Oracle version is installed.

3. Oracle listener is running on alternate host.

4. Protocol and storage stack is same.

Regards,

Himanshu

Re: SMO 32-bit error on 64-bit system

Thanks Himanshu,

I am cloning the database to an alternate host.

1. Architecture and OS ( and version) are same on both the hosts-->the architecture and the O/S versions are the same.

2. Same Oracle version is installed-->the oracle version is the same.

3. Oracle listener is running on alternate host-->the listener is running fine.

4. Protocol and storage stack is same---the protocol and the storage stack is the same.

How is SMO setup the environment variables during the cloning?

Thanks for the reply.

Re: SMO 32-bit error on 64-bit system

Phuti,

Environment variables are derived from user input Oracle_home specified in the clone wizard.

Thanks,

Himanshu

Re: SMO 32-bit error on 64-bit system

Thanks Himanshu,

Which config file is smo use to set up those environment variables?

Our sys admin upgraded the following:

SANToolKit  from 5.1 to 6.0

SnapDrive    from 4.2 to 4.2P3

SMO           from 3.1 to 3.1P6

But when we try to clone our databases from one server to the another we get these errors:

SP2-1503: Unable to initialize Oracle call interface

SP2-0152: ORACLE may not be functioning properly

When I simulate the error on the server it looks like we have an issue with the LD_LIBRARY_PATH.

How can I remedy this issue?

Thanks