.ora-code.com

Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
windows database service not shutting down database on reboot

windows database service not shutting down database on reboot

2006-06-06       - By Joe Armstrong-Champ
Reply:     1     2     3     4     5     6  

Paul,

I haven't tried increasing the timeout. Seems like the credentials
failure wouldn't be helped by that, but I may try it.

The service is running under local system. I think I'll change it to a
user that's in ora_dba.

Thanks.

> Did you do any mucking about in the registry regarding
>
> HKLM\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout
>
> The default value is only 20 seconds (20000), which was likely fine for
> a 7.3.4 database using say 128 MB of physical memory and perhaps a
> single job queue process.
>
> A 10g R1 database instance using say 1.7 GB of physical memory may take
> quite awhile to shutdown cleanly from a shutdown immediate. Perhaps the
> following would help:
>
> oradim -edit -sid mydb -shutmode a
>
> or if you don't want to go the route of shutdown abort when the serivce
> is stopped:
>
> oradim -edit -sid mydb -timeout 600
>
> This won't help in the case of a hard shutdown (power-off by BOFH, ups
> runs out of juice, etc).
> It also won't help with your current symptoms.
>
> The re-create the serivce and apply the latest patchset are probably the
> first 2 lines off of their script for this issue.
>
> What credentials is the OS service running under? (localsystem, service
> account with membership in the local OS ORA_DBA group, service account
> with membership in the local OS ORA_MYDB_DBA group, etc)
>
> Paul
--
http://www.freelists.org/webpage/oracle-l