| db locking [message #56692] |
Wed, 16 April 2003 16:56  |
akymx@hotmail.com
Messages: 3
Registered: April 2003
|
Junior Member |
|
|
Please help.
I am experiencing this problem:
When I launch my front end application and try to access a record, no data will display in the frame, and when I launch SQL*PLUS it will freeze.
But when I launch my oracle db I can access the table and display the record I was trying to see in the front end application.
I have checked my alert and trace file for errors but nothing. I have also stop and start my services without much susccess.
Any help will be greatly appreciated.
Thanks.
Akym
|
|
|
|
| Re: db locking [message #56694 is a reply to message #56692] |
Thu, 17 April 2003 01:46  |
psmyth
Messages: 81
Registered: October 2002
|
Member |
|
|
|
check available disk space, and your archive logs... are you running in archivelog mode? have you specified the archive log parameters correctly in the init.ora file?
|
|
|
|
| Re: db locking [message #56700 is a reply to message #56692] |
Thu, 17 April 2003 08:45 |
akym
Messages: 4
Registered: April 2003
|
Junior Member |
|
|
Psmyth,
The db is running on archive log mode, but the db repository was not. I got this when I run this cmd:
SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination C:oracleora90RDBMS
Oldest online log sequence 78
Current log sequence 80
When I tried to put the repository db on archive mode I get this exception message:
"The exception (org.omg.CORBA.object_Not_Exist) occured"
Any idea?
Thanks a bunch.
|
|
|
|
| Re: db locking [message #56701 is a reply to message #56692] |
Thu, 17 April 2003 09:39 |
psmyth
Messages: 81
Registered: October 2002
|
Member |
|
|
i think you'll need to explain a bit more about whats going on here... whats the repository db got to do with the problem?
I think you can ignore the archive logs as a cause of your problem, as you aren't running the database in archivelog mode. I think you need to check the alert logs etc and any system logs that may be appropriate.
I'm more of a unix person, so can't help too much with this... just thought the space issue might have been an easy solution.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
