This is what I have found out.
1) Snap Creator Framework supports Oracle Plugin on bash only
2) From the IAG,
" The Oracle plug-in supports Oracle 10g database or later versions. The Oracle plug-in uses SQL*Plus to communicate with the database.
To use C Shell (CSH) with the Oracle plug-in on UNIX or Linux platforms, the following conditions
should be met:
• Snap Creator Agent must be started as the Oracle user, instead of the root user.
• The Oracle user must have the proper environmental variables (ORACLE_HOME and ORACLE_SID) set in order for the plug-in driven SQL*Plus commands to work.
This can be done with a shell startup file, such as ~/.cshrc
If your cshrc is not customized to pass different ORACLE_SID, this might inadvertently backup the wrong SID (as in your case, since the shell environmental variables are wrong).
A possible workaround is to set ORACLE_SID from the shell and restarting the scAgent
example
#!/bin/sh
export ORACLE_SID=CDE
$SC_AGENT_HOME/bin/scAgent restart
Note: You may also be able to run Snap Creator agent on different port with the above ORACLE_SID and use that to communicate to CDE.
or, you may be able to use different UNIX user login whose .cshrc is customized for the second ORACLE_SID
Please check if the below information can help as well.
Multiple-Instance System
On a multiple-instance System, include a list of instance names and commands necessary to initialize the oraenv
script at the end of the startup file of the oracle
user account.
Table 4-3 shows the required Bourne or Korn shell commands for initializing the oraenv script on UNIX platforms.
Table 4-3 Bourne/Korn Commands to Initialize the oraenv Script on Multiple-Instance Systems
Solaris |
#!/bin/sh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' |\ grep -v "#" ORAENV_ASK="YES" . /usr/local/bin/oraenv
|
AIX, HP, Linux and Tru64 |
#!/bin/sh echo "The SIDs on this machine are:" cat /etc/oratab | awk -F: '{print $1}' | grep -v "#" ORAENV_ASK="YES" . /usr/local/bin/oraenv
|
Table 4-4 describes the C shell commands for initializing the oraenv script on UNIX platforms.
Table 4-4 C Shell Commands to Initialize the oraenv Script on Multiple-Instance Systems
Solaris |
#!/usr/bin/csh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' |\ grep -v "#" set ORAENV_ASK="YES" source /usr/local/bin/coraenv
|
AIX, HP, Linux and Tru64 |
#!/usr/bin/csh echo "The SIDs on this machine are:" cat /etc/oratab | awk -F: '{print $1}' | grep -v "#" set ORAENV_ASK="YES" source /usr/local/bin/coraenv
|
Multiple-Instance System
On a multiple-instance System, include a list of instance names and commands necessary to initialize the oraenv
script at the end of the startup file of the oracle
user account.
Table 4-3 shows the required Bourne or Korn shell commands for initializing the oraenv script on UNIX platforms.
Table 4-3 Bourne/Korn Commands to Initialize the oraenv Script on Multiple-Instance Systems
Solaris |
#!/bin/sh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' |\ grep -v "#" ORAENV_ASK="YES" . /usr/local/bin/oraenv
|
AIX, HP, Linux and Tru64 |
#!/bin/sh echo "The SIDs on this machine are:" cat /etc/oratab | awk -F: '{print $1}' | grep -v "#" ORAENV_ASK="YES" . /usr/local/bin/oraenv
|
Table 4-4 describes the C shell commands for initializing the oraenv script on UNIX platforms.
Table 4-4 C Shell Commands to Initialize the oraenv Script on Multiple-Instance Systems
Solaris |
#!/usr/bin/csh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' |\ grep -v "#" set ORAENV_ASK="YES" source /usr/local/bin/coraenv
|
AIX, HP, Linux and Tru64 |
#!/usr/bin/csh echo "The SIDs on this machine are:" cat /etc/oratab | awk -F: '{print $1}' | grep -v "#" set ORAENV_ASK="YES" source /usr/local/bin/coraenv
|