asked on

Grid will not display

Hi,

I am a novice when it comes to Oracle. I am filling in as a temp so please bear with me.
We are running Oralce 10g and I have been managing everythign via the Grid. Now for some reason I keep getting page cannot display when I try to get to the grid.

Thanks,

logictank

Sainai

ASKER

Thank you, I will give this a try. I will get back with you.

Sainai

ASKER

I ran opmnctl status and it keeps giving me an unrecognized command. I ran this as oracle and root and nothing.
I also ran the /etc/init.d/gcstartup start and it says that the agent is still running.

Sainai

ASKER

I looked at my logs and this is what I got. I think this is the problem but where and how do I make space?

ORA-19815: Warning: db_recovery_file_dest_sizeof XXXX
bytes is 100% used and has 0 remaining bytes available.

thanks

logictank

Verify that your oracle user environment is setup correctly to see the opmnctl command ($ORACLE_HOME & $PATH), this file will be under $ORACLE_HOME/opmn/bin. The $ORACLE_HOME variable should point to the Grid Server OMS home, you can also run 'opmctl status' directly from the OMS $ORACLE_HOME/opmn/bin directory:
cd $ORACLE_HOME/opmn/bin
./opmnctl status
If any of the services are down such as HTTP_Server or the OC4J containers you can try stopping and starting the OMS services:
As root:
/etc/init.d/gcstartup stop (Wait for all OMS processes to die or kill manually)
/etc/init.d/gcstartup start (Verify services are up with opmctl status)
If you're still experiencing problems check logs in the OMS Home:
$ORACLE_HOME/sysman/log
$ORACLE_HOME/Apache/Apache/logs
Note: If there are other Oracle services running on this node other than Grid OMS be aware not to kill non Grid OMS processes.

logictank

alter system set db_recovery_file_dest_size=100G scope=both; (If using spfile)
Otherwise:
alter system set db_recovery_file_dest_size=100G; (Update pfile manually to maintain setting for next DB restart).
Note: The size of 100G is just an example, set it to your desired value depending on your available storage space.

logictank

Additional:
If you don't have available storage space to grow the db_recovery_file_dest_size value you'll need to either allocate additional storage space or start removing archivelogs and backupsets as necessary. You can also run the "crosscheck" command from RMAN:
crosscheck backupset;
crosscheck copy;
crosscheck archivelog all;
as well as the delete command:
delete noprompt obsolete;
delete noprompt expired backup;
delete noprompt expired copy;
and set a retention policy in RMAN using the "configure retention policy" command.

Sainai

ASKER

Thanks a bunch. I will try your suggestions and get back with you in a few.

Sainai

ASKER

Ok I realize that I am unable to use the alter command because I cannot get in as Ops Oracle, System or anything. I am also getting this error when I run the crosscheck:
Not connected to the target database. It seems the db is down. I tried using the crs_start command as well as the srvctl command to start it and it won't come up. I think the error ORA-19815: Warning: db_recovery_file_dest_sizeof XXXX
bytes is 100% used and has 0 remaining bytes available." is preventing me from doing so.

any suggestions so I can get the db up so I can later the spfile?
thanks a bunch

ASKER CERTIFIED SOLUTION

logictank

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Sainai

ASKER

Tanks LogicTank I'll give it another go. I'll get back with you.

thanks