Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> TWO_TASK in Oracle 7.3.4 does not work, Any ideas ?
Hi folks,
We have Oracle 7.3.3 on Solaris 2.5.1. The database ORACLE_HOME is
../.../7.3.3
We are still using SQL*forms30 and SQL*Menu50 and its ORACLE_HOME is
../.../7.2.3
To handle this situation we have used TWO_TASK. It has worked very well in past 1 year or more.
I was upgrading to 7.3.4 and on the test machine I did the upgrade with the
usual running of catalog.sql,
catproc.sql and importing from the old databse etc. and everything looks
good except the TWO_TASK
portion of it.
Here are the scenarios. SCAD is the old 7.3.3 database instance and SCAN is the new 7.3.4 database instance. I have both the instances up and running on the machine.
ORACLE_HOME=.../.../7.3.4; export ORACLE_HOME
ORACLE_SID=SCAN; export ORACLE_SID
unset TWO_TASK
This is the setting we used for the old 7.3.3 database instance for the
users who are using forms.
It even works now for 7.3.3 database instance if I change TWO_TASK=SCAD.
ORACLE_HOME=.../.../7.2.3; export ORACLE_HOME
TWO_TASK=SCAN; export TWO_TASK
unset ORACLE_SID
When you try to use sqlplus, you get the following error:
Enter user-name:
I have used the same tnsnames.ora file(s) that has SCAD and added SCAN to
those file(s). AFAIK I need it only in
.../.../7.2.3/network/admin/tnsnames.ora, but the previous DBA has it also
in
.../.../7.3.3/network/admin/tnsnames.ora. I also added it to
../.../7.3.4/network/admin/tnsnames.ora.
I added SCAN to the /var/opt/oracle/listener.ora SID_LIST and pointing to
../.../7.3.4 for ORACLE_HOME and SCAN for ORACLE_SID.
Then, I stopped the listener and started it. I did this under both 7.3.3 and 7.3.4 but it did not help.
The error ORA-01034 says:
Cause ORACLE was not started up. Possible causes are:
.............. .............. BUT THIS IS NOT CORRECT, BECAUSE I CAN CONNECT TO THE INSTANCE SCAN VIA THE FIRST SCENARIO and also ps -ef |grep SCAN shows all processesrunning.
The error ORA-07429 says:
Cause A shared memory segment used for all part of the SGA could not be retrieved.
Action Use the system error number in the error message to determine why the segment could not
be retrieved. If it does not exist, shut down the database using the abort option, and then
restart it. If the get failed because the permissions are incorrect, make sure that ownership of
the oracle executable is the same as that on the shared memory segment.
I have aborted the instance and restarted with the same results.
Any ideas as to what the problem is ?
Thanks for your input.
Suresh Bhat
DBA
Received on Fri Oct 01 1999 - 08:51:24 CDT
![]() |
![]() |