FRM-92050 Error with Internet Explorer-8

While using oracle applications R12 with Internet Explrer 8 an Form Server related error is encountered (FRM-92050: Failed to connect to the server).To, avoid this problem Disable the XSS Filter option in IE8.

Tools--> Internet options--> Security-->Security level for this zone --> Custom level-->Disable XSS filter

Now there is no issue with Error FRM-92050

Errors: ORA-01552 ORA-00376 ORA-01110 ORA-01548 –UNDO tablespace

Recently our Helpdesk people configured backup on Payroll server. while running the backup, backup applications locking the writing file.for that issue alert log showing errors like below:

Mon Jul 06 05:07:36 2009
KCF: write/open error block=0x6f6 online=1
file=2 D:\ORACLE9\PRODUCT\PAYROLL\ORADATA\PAYROLL9\UNDOTBS01.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
Automatic datafile offline due to write error on
file 2: D:\ORACLE9\PRODUCT\PAYROLL\ORADATA\PAYROLL9\UNDOTBS01.DBF
Mon Jul 06 05:07:36 2009
Errors in file d:\oracle9\product\payroll\admin\payroll9\bdump\payroll9_smon_2700.trc:
ORA-00376: file 2 cannot be read at this time
ORA-01110: data file 2: 'D:\ORACLE9\PRODUCT\PAYROLL\ORADATA\PAYROLL9\UNDOTBS01.DBF'

Immediately we stopped the backup & restarted the database .
Still the Application is not working. Application show error message

"ORA-01552: cannot use system rollback segment for non-system tablespace"

then I checked for the corrupted rollback segments

SQL>select segment_name,status,tablespace_name from dba_rollback_segs where status='NEEDS RECOVERY';
SEGMENT_NAME STATUS TABLESPACE_NAME
------------------------------ ---------------- -----------------
_SYSSMU1$ NEEDS RECOVERY UNDOTBS1
_SYSSMU2$ NEEDS RECOVERY UNDOTBS1
_SYSSMU3$ NEEDS RECOVERY UNDOTBS1
_SYSSMU4$ NEEDS RECOVERY UNDOTBS1
_SYSSMU5$ NEEDS RECOVERY UNDOTBS1
_SYSSMU6$ NEEDS RECOVERY UNDOTBS1
_SYSSMU7$ NEEDS RECOVERY UNDOTBS1
_SYSSMU8$ NEEDS RECOVERY UNDOTBS1
_SYSSMU9$ NEEDS RECOVERY UNDOTBS1
_SYSSMU10$ NEEDS RECOVERY UNDOTBS1

then I recreated another tablespace as UNDOTBS2

CREATE UNDO TABLESPACE "UNDOTBS2"
DATAFILE 'D:\ORACLE9\PRODUCT\PAYROLL\ORADATA\PAYROLL9\UNDOTBS02.DBF' SIZE 200M REUSE
AUTOEXTEND ON NEXT 51200K MAXSIZE 800M;

ALTER SYSTEM SET undo_tablespace=UNDOTBS2 SCOPE=BOTH;

Now I try to drop the old UNDO tablespace but it’s giving error:

ora-01548 active rollback segment found

Now the issue is resolved but in Alert log we are getting errors like:

Wed Jul 15 11:50:52 2009
SMON: about to recover undo segment 1
SMON: mark undo segment 1 as needs recovery
……..
SMON: about to recover undo segment 10
SMON: mark undo segment 10 as needs recovery

& for some transactions from applications we are getting some more errors:

ORA-00376: file 2 cannot be read at this tme ORA-01110: data file 2: 'D:\ORACLE9\PRODUCT\PAYROLL\ORADATA\PAYROLL9\UNDOTBS01.DBF'

Solution:
1. create pfile from spfile;

2. Add the following line to pfile:

_corrupted_rollback_segments =('_SYSSMU1$','_SYSSMU2$','_SYSSMU3$','_SYSSMU4$',
'_SYSSMU5$','_SYSSMU6$','_SYSSMU7$','_SYSSMU8$','_SYSSMU9$','_SYSSMU10$')

_OFFLINE_ROLLBACK_SEGMENTS=('_SYSSMU1$','_SYSSMU2$','_SYSSMU3$','_SYSSMU4$','_SYSSMU5$','_SYSSMU6$','_SYSSMU7$','_SYSSMU8$','_SYSSMU9$','_SYSSMU10$')

3. comment undo management-Auto

#undo_management=AUTO

4. create spfile from pfile

5. Start the database again:

SQL> STARTUP RESTRICT

6. Drop bad rollback segments

SQL> drop rollback segment "_SYSSMU11$";
Rollback segment dropped.
......
SQL> drop rollback segment "_SYSSMU10$";
Rollback segment dropped.

7. Check again

SQL> select segment_name,status,tablespace_name from dba_rollback_segs where status='NEEDS RECOVERY';

No rows returned

8. DROP TABLESPACE undotbs1 INCLUDING CONTENTS AND DATAFILES ;

9. shutdown immedaite

10. remove added lines & comments from pfile and recreate the spfile

11.startup

Now the issue is resolved.

IOR file '/var/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located

While login to the Solaris as root or any other user it’s showing the errors like below:

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: IOR file '/var/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/var/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: No such file or directory)

I had checked the /var/tmp/gconfd-root directory permissions

it has 777 permissions for that directory

while i checked log under /var/log it says: 777 is bad option for gconfd-root
I had changed that permissions to 700 and all seems ok now.

now it’s working fine

ORA-20100: Error: FND_FILE FAILURE unable to create file in the directory,/usr/tmp.

Concurrent requests are failed with the below error:

ORA-20100: Error: FND_FILE failure. Unable to create file, o0040178.tmp in thedirectory, /usr/tmp.

You will find more information in the request log.
ORA-06512: at "APPS.FND_FILE", line 417
ORA-06512: at "APPS.FND_FILE", line 456
ORA-06512: at line 1

Upon checking below settings there is no issue :

1. The $APPLTMP, $APPLPTMP variables and UTL_FILE_DIR database parameter are valid and pointing to directory where there is enough space and users have written permission.
2. FND_FILE.PUT_LINE is able to create new files in the temporary directory.

FND_FILE.PUT_LINE Checking method:

SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST');

This should dump a file on APPLPTMP. If this test works, it would indicate that FND_FILE is ok and the problem is possibly with the Application.

You may want to leave only one entry on utl_file_dir for this test.

finally I checked the utl_file_dir, but there is no entry like /usr/tmp path in that list

SQL> connect / as sysdbaSQL> show parameter UTL_FILE_DIR

just I added /usr/tmp for the UTL_FILE_DIR & restarted the applications & database.

now the issue is resolved & concurrent requests are working fine

TNS listener failed to start with 12546 , 12560 , 00516 & Solaris Error: 13: Permission denied errors

while starting the database listener, listener is failed with errors.

LSNRCTL> start VIS
Starting /data2/oracle/VIS/db/tech_st/10.2.0/bin/tnslsnr: please wait...

TNSLSNR for Solaris: Version 10.2.0.3.0 - Production

System parameter file is /data2/oracle/VIS/db/tech_st/10.2.0/network/admin/VIS_aplerp6/listener.ora

Log messages written to /data2/oracle/VIS/db/tech_st/10.2.0/network/admin/vis.log

Error listening on: (ADDRESS=(PROTOCOL=ipc)(PARTIAL=yes)(QUEUESIZE=1))

No longer listening on:

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=aplerp6.apl.com)(PORT=1522)))

TNS-12546: TNS:permission denied

TNS-12560: TNS:protocol adapter error

TNS-00516: Permission denied

Solaris Error: 13: Permission denied

Listener failed to start. See the error message(s) above...

cause:
.oracle read, write permissions are changed
solution
cd /var/tmp
chmod 777 .oracle
now the issue is resolved & listener stared .

ORA-29282: invalid file ID. ORA-06512: at "SYS.UTL_FILE", line 1

During the 12.0.6 to 12.1.1 upgrade , Main patch (7303030 -12.1.1 Maintenance Pack) is failed with the below error:

Error message in the worker logs is:-
DECLARE*ERROR at line 1:
ORA-29282: invalid file ID
ORA-06512: at "SYS.UTL_FILE",
line 1ORA-06512: at line 41
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE",
line 449ORA-29283: invalid file operation

Cause:
In this case the utl_file_dir was set to /usr/tmp for both instances.

The utl_file package does not give a suitable error message when it finds an existing file with the same name as the file it is attempting to write.

The same errors can be reported when the system does not have permissions to write to the utl_file_dir.

Solution:
Change the utl_file_dir variable in both init.ora files for each instance and bounce the RDBMS.

Initially Instance-VIS and Instance-CRP both had utl_file_dir=/usr/tmp .

They should be set to something like:-

For VIS Instance- utl_file_dir=/usr/tmp/VIS/

For CRP Instance- utl_file_dir=/usr/tmp/CRP/

ORA-12701: CREATE DATABASE character set is not known

While Starting the database, I had faced the error - ORA-1092 signalled during: ALTER DATABASE OPEN...
then check in the Alert.log it shows the messages like below:
ORA-12701: CREATE DATABASE character set is not known
Thu Jul 9 19:10:14 2009
Error 12701 happened during db open, shutting down database
USER: terminating instance due to error 12701
Instance terminated by USER, pid = 28018
ORA-1092 signalled during: ALTER DATABASE OPEN...

Solution:
I had checked $ORA_NLS10 path. Instead of “$ORACLE_HOME/nls/data/9idata”,
it points to the Wrong one like below:

echo $ORA_NLS10
ORA_NLS10=/aplvol01/CRP/oracle/CRP/db/tech_st/10.2.0/ocommon/nls/admin/data

Change the env file to the correct path and start the database.

wferr: - 1602: Could not save. - 1400: Could not save to database. MODE=UPGRADE EFFDATE=

While Applying the 8310984 - May 2009, Order Management R12 Cumulative Patch on R12.0.6, worker is failed with the below mentioned error:

ATTENTION: All workers either have failed or are waiting:
FAILED: file oexwford.wft on worker 1.
Worker Log file:
wferr:
- 1602: Could not save.
- 1400: Could not save to database. MODE=UPGRADE EFFDATE=
- 1404: Please first load this entity or check protect and custom level of ACTIVITY 'WFSTD/FED_BUILD_PA_AP_INVO_ACCT_GEN'.
Oracle Workflow Definition Loader 2.6.4.0.
Access level: 20, Mode: UPGRADE
ITEM_TYPE 'WFSTD' is protected, no changes were saved.
ITEM_ATTRIBUTE 'WFSTD/EVENTNAME' is protected, no changes were saved.
ITEM_ATTRIBUTE 'WFSTD/REQUESTOR_USERNAME' is protected, no changes were saved.
ITEM_ATTRIBUTE 'WFSTD/OWNER_ROLE' is protected, no changes were saved.
ITEM_ATTRIBUTE 'WFSTD/FORWARD_FROM_DISPLAY_NAME' is protected, no changes were saved.
ITEM_ATTRIBUTE 'WFSTD/N' is protected, no changes were saved.

Solution:
Change the Patch driver file related WFLOAD command from UPGRADE to FORCE.

Before Modify:
# file-version-parsed ont patch/115/import/US oexwford.wft 120.8.12000000.10

exec fnd bin WFLOAD bin &phase=daa+52 checkfile:ont:patch/115/import/US:oexwford.wft &ui_apps 0 Y UPGRADE @ONT:patch/115/import/US/oexwford.wft

After Modify:
# file-version-parsed ont patch/115/import/US oexwford.wft 120.8.12000000.10

exec fnd bin WFLOAD bin &phase=daa+52 checkfile:ont:patch/115/import/US:oexwford.wft &ui_apps 0 Y FORCE @ONT:patch/115/import/US/oexwford.wft