Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle 8.0.4 returns 7497 error

Oracle 8.0.4 returns 7497 error

Hello:

We´ve got a ORACLE 8.0.4 Database running in a HPD230 machine.

PRO*C process aborted last morning while trying to connect to database. Oracle returns 7497 error:

contal1 18: oerr ora 7497
07497, 00000, "sdpri: cannot create trace file '%s'; errno = %s."
// *Cause: The trace file cannot be created for writing.
// *Action: Check if the dump directory exists and whether it is writable.

I reviewed dump directories and it seems to be OK... can anyone help?

Thank
11 REPLIES
Joseph Loo
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

hi,

could you do reply on the output of this kernel parameter?

# kmtune -q maxfiles

it seems HP-UX kernel parameter, MAXFILES, limit has been exceeded, accordingly to Oracle Metalink DocID 145437.1. Also read 1011677.6 if you have access to Metalink.

regards.
what you do not see does not mean you should not believe

Re: Oracle 8.0.4 returns 7497 error

Sorry Joseph, we don´t have kmtune command, it´s a 10.20 machine.

Sysdef returns:

maxdsiz 16384 - 256-655360 Pages -
maxfiles 2048 - 30-2048 -
maxfiles_lim 2048 - 30-2048 -
maxssiz 2048 - 256-655360 Pages -

Attached is full sysdef return, tha
Joseph Loo
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

hi,

check file descriptor:

# ulimit -n
should return 2048

are there any other accompanying error message beside ORA-07497?

regards.
what you do not see does not mean you should not believe
Jean-Luc Oudart
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

Hi,

which user receives this message ?
(oracle process owner)

Have you try to run a trace as user oracle (trace current session) and look for the file to validate dump directory. May not be the expected one. cf. thread :
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=541980

Regards,
Jean-Luc
fiat lux

Re: Oracle 8.0.4 returns 7497 error

Joseph:

ulimit returns 2048 as you suggested, there is no other message than posted one.

Luc:

SQL> select name,value from v$parameter where name like '%dump%';

NAME VALUE
---------------------------------------
shadow_core_dump full
background_core_dump full
background_dump_dest /oracle/admin/contal/bdump
user_dump_dest /oracle/admin/contal/udump
max_dump_file_size 10240
core_dump_dest /oracle/admin/contal/cdump

6 rows selected.

Dump directories exists... and all seem to be OK (permissions...).

User who receives the message is not oracle.

Any other thing to check?

Thanks.
Nicolas Dumeige
Esteemed Contributor

Re: Oracle 8.0.4 returns 7497 error

Manuel,

Very obvious one but whatever : have you checked the space on the device ?
Do you see any syslog entries on filesystem full ?

Cheers,

Nicolas
All different, all Unix
Jean-Luc Oudart
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

Manuel,

Could you try to run a session as user oracle (connect as user system)
alter session set SQL_TRACE=TRUE;
select user from dual;

exit and check for the trace file. What is the location of such file ?

Regards,
Jean-Luc
fiat lux

Re: Oracle 8.0.4 returns 7497 error

Nicolas,

I checked space on device and it seems to be OK, I´ll re-check syslog looking for any clue.

Jean-Luc,

Trace files are stored in /oracle/rdbms/log, we used themseveral times for "tkprofing".

Do you see any problem with trace?
It´s the first time this problem appears in 3 years
Indira Aramandla
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

Hi Manuel Gomez,

The error that you are experiencing ORA 7497 sdpri: cannot create trace file '%s'; errno = %s. implies that the trace file cannot be created for writing.

For this you need to check the USER_DUMP_DEST and BACKGROUND_DUMP_DEST settings point to a valid writable directory. And also check these settings do NOT include an environment variable. Ie: Use full explicit pathnames for these parameters. Check for full OS kernel tables

From the above replies / suggestions looks like all these had been done. ORA-7497 sdpri: cannot create trace file '', errno=. with no information is possibly exhaustion of the file descriptors allowed for a given process OR for the system in total. Check any user limits on file descriptors and raise these.

When you say the user getting this error is ont ORACLE user, did you check manually if you can create a file as that user in the expected directory (oracle/admin/contal/udump and /oracle/rdbms/log) and check if you can create a LARGE file there manually.

And when you say it occurred for the first time since 3 years, was this user able to connect to the database with ProC process before.


Indira A
Never give up, Keep Trying

Re: Oracle 8.0.4 returns 7497 error

Indira:

Some answers to your questions:

- USER_DUMP_DEST & BACKGROUND_DUMP_DEST are directories belonging to oracle os user and no other user can write on them. They doesn´t include env. variables on his names but full explicit names.

- About user limits on file descriptors.. I need a bit more help on that, any kernel parameter to check, log to inspect...?

- I checked manually trc file creation and it works, but no other than oracle user can create a file on /oracle/admin/contal/udump.

- And finally and most misterious... PRO*C process that fails, runs 48 times in a day 365 days in a year... and it worked OK in 3 years. In fact it connected to database next time it runned after the fialure...

Any other suggestion?
Thanks all guy
Indira Aramandla
Honored Contributor

Re: Oracle 8.0.4 returns 7497 error

Hi Manuel,

From your reply, can I assume that now you are not experiencing this problem. Because you said Pro*C process connected to the database after the failure.

The reason I mentioned about file descriptor limitation is it could be a possibility (not sure may be) as the error 7497 sdpri: cannot create trace file '', errno=.and there is not error number displayed, so may be there is exhaustion of the file descriptors allowed for a given process OR for the system in total. May be this is not the reason, but just possibility.

For Eg:-
The requirement for file descriptors is not specific to Oracle. Other applications running on that server might be requiring the same resource.You need to account for them also.

For Oracle, you can arrive at a rough estimate as follows:

No of datafiles * 2 + Provision for controlfiles + provision for log files + Some buffer.

Eg:

If db_files = 200 and you have 3 copies of controlfiles and 3
sets of log files, roughly you would need

200 * 2 + 3 + 3 + 50 = 456

If you have more than one instance, you need to add the requirements for each instance to arrive at the total requirement for Oracle.

Attached is a document which describes How to Display and Change UNIX Process Resource Limits.


Indira A
Never give up, Keep Trying