Linux CPIO command for Extracting files

$ cpio -idmv <Filename (No space after the redirection "<" sign)

The "-i" flag is for extract,
the "-d" flag creates directories ahead of time if necessary,
the "-m" flag is to preserve modification times on the restored files, and
the "-v" flag performs the whole operation in verbose mode in the end giving you the total extracted blocks.

Oracle 10g Restricted mode

Before 10g, startup restrict would allow only users with restricted session to connect to the database. With 10g, the listener 'knows' if the database is in restricted mode and will disallow any TNS connects. Even the dba would have to be on the database host and log in as sysdba.

There is a work-around, however. If you add "(UR=A)" to the CONNECT_DATA portion of your connect string definition (MetaLink Doc ID 44120.1).

SQL Server Agent Autostart

SQL Server Agent Service won't Autostart, eventhough when you right click properties and select => General page, the "Auto restart SQL Server if it stops unexpectedly" and "Auto restart SQL Server Agent if it stops unexpectedly" boxes are checked.

Solution - Navigate - Start -> All Programs -> Microsoft SQL Server 2xxx -> Configuration Tools -> SQL Server Configuration Manager

Select "SQL Server Services" Node in the left pane to see the related SQL Server services in the right pane. Right Click on the "SQL Server Agent (INSTANCE)" under "Name" in Right pane and select "Properties". Go to "Service" tab, check and edit the setting against "Start Mode" parameter. This should fix the issue.

ORA-19815

ORA-19815: WARNING db_recovery_file_dest_size of xxx is yyy% used...

RMAN and/or the archiver is running out or IS out of space on the db_recovery_file_dest. If you remove files from that location with OS commands, remember to crosscheck and delete expired files from within RMAN. If that still doesn't resolve the problem, you may need to increase the db_recovery_file_dest_size.

If you started the database with an spfile, then
alter system set db_recovery_file_dest_size=zzzG scope=both;
should fix you right up, assuming of course, you HAVE zzz GB available.

Links:
http://www.eygle.com/archives/2005/12/oracle_diagnost_howto_deal_ora-19815.html

And here we go...

Welcome to the Shared Pool. Nothing fancy, just a collection of notes, links, solutions and whatever else strikes my fancy about database administration. With all the resources available, I'm not trying to add anything new to the collection; rather, just a simple notebook for my colleagues and myself to keep track of interesting tidbits.