Warning: log write time

After upgrading to 10.2.0.4, we started seeing messages in alert log

*** 2009-10-27 11:12:26.575
Warning: log write time 590ms, size 22KB

Metalink Note 601316.1 describes this issue. LGWR starts producing trace files with this kind of information:

Elapsed times include waiting on following events:

Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
SQL*Net message to client 3 0.00 0.00
SQL*Net message from client 3 0.00 0.00
db file sequential read 7080 3.83 196.43
latch: session allocation 1 0.00 0.00
read by other session 2 0.53 0.59
latch free 1 0.00 0.00

*** 2009-10-27 11:12:26.575
Warning: log write time 590ms, size 22KB
*** 2009-10-27 11:12:28.294
Warning: log write time 610ms, size 43KB
*** 2009-10-27 11:12:30.257
Warning: log write time 570ms, size 69KB
*** 2009-10-27 11:12:47.335
Warning: log write time 700ms, size 2213KB
*** 2009-10-27 11:14:02.255
Warning: log write time 560ms, size 1372KB
*** 2009-10-27 11:14:03.104
Warning: log write time 850ms, size 2823KB
*** 2009-10-27 11:16:10.756
Warning: log write time 640ms, size 261KB
*** 2009-10-27 11:16:51.149
Warning: log write time 500ms, size 1703KB
*** 2009-10-27 11:16:51.800
Warning: log write time 650ms, size 3317KB

As per the note

These messages are very much expected in 10.2.0.4 database in case the log write is more than 500 ms.

This is a warning which means that the write process is not as fast as it intented to be. So probably you need to check if the disk is slow or not or for any potential OS causes. If everything looks fine at the hardware level or OS level then you can safely ignore these messages.

The trace file can easily be deleted or truncated.

How to download password protected patch from updates.oracle.com

Akhilesh asked me this question today. A metalink search revealed note 731257.1 which has the details. In short before issuing the get command you are required to issue the command site protected .

In fact if you directly issue the get command you get the error message which says the same:

ftp> bin
g200 TYPE changed to I.
ftp> et p8995444_11i_d.zip
200 PORT command OK.
550-File or directory not found.
550-This is a password protected patch.
550-Enter the password with site command:
550-quote site protected
550 Then get the patch again.

After issuing the site protected command it worked

ftp> site protected V5pIHQqk
200 The password was received successfully.
ftp> get p8995444_11i_d.zip
200 PORT command OK.
150 Opening BINARY mode data connection for file p8995444_11i_d.zip.

It worked with quote site protected command also:

ftp> quote site protected V5pIHQqk
200 The password was received successfully.
ftp> get p8995444_11i_d.zip
200 PORT command OK.
150 Opening BINARY mode data connection for file p8995444_11i_d.zip.

This is of limited use now as Oracle is decomissioning their ftp service and you'll need to use wget and URL from the patch download button in new metalink.

R12.1.1 Apache won't start libopmnoraclenls.so unable to load

After R12.1.1 install, Apache wouldn't start and we had these errors in the log

libopmnoraclenls.so unable to load

One of the metalink notes advised running genclntsh on IAS_ORACLE_HOME.

$ ./genclntsh -32
cat: cannot open $IAS_ORACLE_HOME/lib32/ldflags
Undefined first referenced
symbol in file
nnfhboot $IAS_ORACLE_HOME/lib32/libn10.a(nnfgt.o)
nnflboot $IAS_ORACLE_HOME/lib32/libn10.a(nnfgt.o)
nnflgapc $IAS_ORACLE_HOME/lib32/libnl10.a(nlpa.o)
nnftboot $IAS_ORACLE_HOME/lib32/libn10.a(nnfgt.o)
nnflgav $IAS_ORACLE_HOME/lib32/libnl10.a(nlol.o)
nnflfrm $IAS_ORACLE_HOME/lib32/libnl10.a(nlol.o)
nnflrne $IAS_ORACLE_HOME/lib32/libnl10.a(nlol.o)
ntusini $IAS_ORACLE_HOME/lib32/libn10.a(ntcontab.o)
ntpini $IAS_ORACLE_HOME/lib32/libn10.a(ntcontab.o)
nttini $IAS_ORACLE_HOME/lib32/libn10.a(ntcontab.o)
ntzini $IAS_ORACLE_HOME/lib32/libn10.a(ntcontab.o)
ld: fatal: Symbol referencing errors. No output written to $IAS_ORACLE_HOME/lib32/libclntsh.so.10.1


We went through release notes for 12.1.1 present in Metalink note 798258.1 again and
unzipped the Rapidwiz patch 8626041 in stage and reinstalled, but we still faced the same issue.

One of the metalink notes mentioned recreating softlinks, so I checked the soft links and found that Oracle stage had hardcoded softlinks pointing to a mount name /d4/R12/ab/apps/R1211XB9 most probably on Oracle's test servers.

$ ls -ltr |grep d4
lrwxrwxrwx 1 applmgr dba 56 Sep 29 16:58 ldflags -> /d4/R12/ab/apps /R1211XB9/apps/tech_st/10.1.3/lib/ldflags
lrwxrwxrwx 1 applmgr dba 66 Sep 29 16:59 libocci.so -> /d4/R12/ab/a pps/R1211XB9/apps/tech_st/10.1.3/lib32/libocci.so.10.1


$ ls -ltr |grep d4
lrwxrwxrwx 1 applmgr dba 63 Sep 29 16:58 hsdb_odbc.so -> /d4/R12/ab/apps/R1211XB9/apps/tech_st/10.1.3/lib32/hsdb_odbc.so
lrwxrwxrwx 1 applmgr dba 63 Sep 29 16:58 hsdb_oing.so -> /d4/R12/ab/apps/R1211XB9/apps/tech_st/10.1.3/lib32/hsdb_oing.so
lrwxrwxrwx 1 applmgr dba 62 Sep 29 16:58 hsdb_ora.so -> /d4/R12/ab/apps/R1211XB9/apps/tech_st/10.1.3/lib32/hsdb_ora.so
lrwxrwxrwx 1 applmgr dba 62 Sep 29 16:58 hsdb_syb.so -> /d4/R12/ab/apps/R1211XB9/apps/tech_st/10.1.3/lib32/hsdb_syb.so
lrwxrwxrwx 1 applmgr dba 62 Sep 29 16:59 libnavhoa.a -> /d4/R12/ab/apps/R1211XB9/apps/tech_st/10.1.3/lib32/libnavhoa.a
applmgr@tsgsd2106 $ pwd
$IAS_ORACLE_HOME/lib

Once we removed these soft links and pointed them to the existing mounts, we were able to run relink all on 10.1.2 and 10.1.3 homes.

Apache started without issues after we did relink all on 10.1.3 IAS_ORACLE_HOME.

unable to get pty!

Recently on a Solaris 8 box when I executed this command, I go the error unable to get pty

$ /usr/dt/bin/dtterm &
[1] 7507
$ grantpt: Error 0
Warning:
Name: dtTerm
Class: DtTerm
unable to get pty

A google search returned this link from docs.sun.com:

http://docs.sun.com/app/docs/doc/806-1075/6jacsnin4?a=view

unable to get pty!

Cause
When trying to open a Terminal window (dtterm) in CDE, a pop-up window appears stating, Unable to get pty!

dtterm is not able to open /dev/pts/int (where int is an integer). The user cannot open this file because grantpt(3C) failed to change the permissions on the file. grantpt(3C) failed because the binary /usr/lib/pt_chmod is not setuid root. The permissions on /usr/lib/pt_chmod must be 4111.

Action
To restore the correct permissions to pt_chmod, use the following command (as root):

# chmod 4111 /usr/lib/pt_chmod

So I logged in as root and executed the above command.

Issue was resolved.

You are not authorized to access this site.

On accessing Extranet URL from Internet, we got this message:

Access Denied

You are not authorized to access this site.

The application you are attempting to access requires additional authorization. If you feel you have received this message in error, please contact your local business Help Desk.

This error is coming because we have SSO enabled our Extranet also. If the user exists in the SSO database and doesn't exist in the FND_USER table of Oracle E-Business Suite, this error would appear.

After creating the users locally in E-Business Suite, this error should disappear.

ORA-01031: insufficient privileges

Recently we implemented a third party software for Mobile users called Ventureforth Mi2k Server. After doing the install which creates a custom schema and creates packages which call Oracle API to insert, update, delete data into APPS, we got this error when they executed a test call:

ORA-01031: insufficient privileges

We had a tough time figuring out which object didn't have the grant. After a lot of trials through Toad debugging and tracing through DBMS_SYSTEM, I recalled that we could trap any error message in alert log and get more details about the error by using this command:

alter system set events '1031 trace name errorstack level 3';

Here 1031 is ORA-01031. You can put any error code in this command by removing the 0 prefix from the error code. Once you execute this command as SYS/SYSTEM, anytime ORA-1031 is issued by the database, the alert log will record this error and a trace file will be generated to give more details about the error.

Once we did this, we immediately came to know that it was failing when the API was calling UPDATE APPS.JTF_TASK_ALL_RESPONSIBILITIES which was a synonym to JTF.JTF_TASK_RESPONSIBILITIES. The custom schema had rights on JTF.JTF_TASK_RESPONSIBILITIES but not on JTF_TASK_ALL_RESPONSIBILITIES synonym. So we granted the rights:

grant all on APPS.JTF_TASK_ALL_RESPONSIBILITIES TO I2K;

After this the error disappeared.