3 replies to this topic

[Surajit]

Hi ,

Our customer who is using Sun OS 5.7, with Oracle 8.1.7 and PROIV 4.6 has encounter error 385. This error is very strange since they have using PROIV with Oracle for a year. It just occur today.

Here is environment setting in Unix;
#------------------------- DATABASE ------------------------------
ORACLE_HOME=/oracle/product/8.1.7 ; export ORACLE_HOME
ORACLE_SID=tyg ; export ORACLE_SID
ORACLE_TERM=$TERM ; export ORACLE_TERM
LD_LIBRARY_PATH=$ORACLE_HOME/lib ; export LD_LIBRARY_PATH
PATH=$ORACLE_HOME/bin:$PATH ; export PATH
#------------------------- GLOVIA ------------------------------
GLOVIA_HOME=/oracle/tyg ; export GLOVIA_HOME
GLOVIA_PRO=/u6/pro4bin/pro ; export GLOVIA_PRO
GLOVIA_DATA=$GLOVIA_HOME/userdata ; export GLOVIA_DATA
#
PATH=/u1/pro4bin:$PATH ; export PATH
#------------------------- PROIV ------------------------------
# Note: Do NOT alter the SQL_DATE_FORMAT parameter unless the Oracle
# parameter NLS_DATE_FORMAT has also been altered
#
CDATE_50=Y ; export CDATE_50
DATE_SC_50=Y ; export DATE_SC_50
SQL_AGGREGATE_KEY=A ; export SQL_AGGREGATE_KEY
SQL_CURSORS=64 ; export SQL_CURSORS
SQL_DATE_FORMAT=MM-DD-YYYY ; export SQL_DATE_FORMAT
SQL_DBNAME=$ORACLE_SID ; export SQL_DBNAME
SQL_DBTYPE=ORACLE ; export SQL_DBTYPE
#
PRODATA=$GLOVIA_HOME/userdata ; export PRODATA
PROPATH=$GLOVIA_HOME/bs ; export PROPATH
#
SUPPRESS_CLOSEWIN=Y ; export SUPPRESS_CLOSEWIN
TP_ROLLBACK=Y ; export TP_ROLLBACK
V22_EODCAN=Y ; export V22_EODCAN

Does anyone have some suggestions to solve it ?

Surajit

[Tony Waszkiewicz]

Surajit,

The first question to ask is, what's changed?

If they have been running for a year it's most likely that something has changed, e.g. a patch or new software added.

regards

[Surajit]

Sorry,

There is a mistake in communication between myself and my colleague.

My colleague just told me to ask about this error on this forum. The information I got was the system's name which is the client's name so I misunderstood that it was the customer's machine.

The truth is ;
1. Here, we have one MS Windows platform server with the application installed for developingt/testing before delivered to customer
2. At customer' site, the server is Sun OS
The followings are what I have just know
3. Some functions can be executed without problem on MS Windows platform but failed on Sun OS (customer's machine)
4. A Unix server (Sun OS) in office here is set up and application/database on MS Windows Server are migrated to this Unix server so that the system will have the similar environment as customer's
5. Now when the installaiton/migration is finish, my colleague test the system and get this error message, so she come to me.

Surajit