Command prompts for Windows

Command prompts for Windows

Control Panel

·         CONTROL: opens the control panel window

·         CONTROL ADMINTOOLS: opens the administrative tools

·         CONTROL KEYBOARD: opens keyboard properties

·         CONTROL COLOUR: opens display properties with the appearance tab

·         CONTROL FOLDERS: opens folder options

·         CONTROL FONTS: opens font policy management

·         CONTROL INTERNATIONAL or INTL.CPL: opens the regional and language option

·         CONTROL MOUSE or MAIN.CPL: opens mouse properties

·         CONTROL USERPASSWORDS: opens user accounts editor

·         CONTROL USERPASSWORDS2 or NETPLWIZ: user account access restrictions

·         CONTROL PRINTERS: opens faxes and printers available

·         APPWIZ.CPL: opens the add or remove programs utility tool

·         OPTIONALFEATURES: opens the add or remove windows component utility

·         DESK.CPL: opens display properties with the themes tab

·         HDWWIZ.CPL: opens add hardware wizard

·         IRPROPS.CPL: infrared utility tool

·         JOY.CP: opens game controllers settings

·         MMSYS.CPL: opens sound and audio device properties with the volume tab

·         SYSDM.CPL: opens system properties

·         TELEPHON.CPL: opens phone and modem options

·         TIMEDATE.CPL: date and time properties

·         WSCUI.CPL: opens Windows Security Center

·         ACCESS.CPL: opens accessibility options

·         WUAUCPL.CPL: opens automatic updates

·         POWERCFG.CPL: opens power options properties

·         AZMAN.MSC: opens authorisation management utility tool

·         CERTMGR.MSC: opens certificate management tool

·         COMPMGMT.MSC: opens the computer management tool

·         COMEXP.MSC or DCOMCNFG: opens the computer services management tool

·         DEVMGMT.MSC: opens device manager

·         EVENTVWR or EVENTVWR.MSC: opens event viewer

·         FSMGMT.MSC: opens shared folders

·         NAPCLCFG.MSC: NAP client configuration utility tool

·         SERVICES.MSC: opens service manager

·         TASKSCHD.MSC or CONTROL SCHEDTASKS: opens schedule tasks manager

·         GPEDIT.MSC: opens group policy utility tool

·         LUSRMGR.MSC: opens local users and groups

·         SECPOL.MSC: opens local security settings

·         CIADV.MSC: opens indexing service

·         NTMSMGR.MSC: removable storage manager

·         NTMSOPRQ.MSC: removable storage operator requests

·         WMIMGMT.MSC: opens (WMI) Window Management Instrumentation

·         PERFMON or PERFMON.MSC: opens the performance monitor

·         MMC: opens empty console

·         MDSCHED: opens memory diagnostics tools

·         DXDIAG: opens DirectX diagnostics tools

·         ODBCAD32: opens ODBC data source administrator

·         REGEDIT or REGEDT32: opens registry editor

·         DRWTSN32: opens Dr. Watson

·         VERIFIER: opens driver verifier manager

·         CLICONFG: opens SQL server client network utility

·         UTILMAN: opens utility manager

·         COLORCPL: opens color management

·         CREDWIZ: back up and recovery tool for user passwords

·         MOBSYNC: opens synchronization center

·         MSCONFIG: opens system configuration utility

·         SYSEDIT: opens system configuration editor (careful while using this command)

·         SYSKEY: Windows account database security management (careful while using this command)

Windows utility and applications

·         EPLORER: opens Windows Explorer

·         IEXPLORER: opens Internet Explorer

·         WAB: opens contacts

·         CHARMAP: opens character map

·         WRITE: opens WordPad

·         NOTEPAD: opens Notepad

·         CALC: opens Calculator

·         CLIPBRD: opens Clipbook Viewer

·         WINCHAT: opens Microsoft Chat Interface

·         SOUNDRECORDER: opens sound recording tool

·         DVDPLAY: run CD or DVD

·         WMPLAYER: opens Windows Media Player

·         MOVIEMK: Opens untitled Windows Movie Maker

·         OSK: opens on-screen keyboard

·         MAGNIFY: opens Magnifier

·         WINCAL: opens Calendar

·         DIALER: opens phone dialer

·         EUDCEDIT: opens Private Character Editor

·         NDVOL: opens the mixer volume

·         RSTRUI : opens Tool System Restore (For Vista only)

·         %WINDIR%\SYSTEM32\RESTORE\rstrui.exe: opens Tool System Restore (for XP only).

·         MSINFO32: Opens System Information

·         MRT : launches the utility removal of malware

·         Taskmgr : Opens the Windows Task Manager

·         CMD: opens a command prompt

·         MIGWIZ: Opens the tool for transferring files and settings from Windows (Vista only)

·         Migwiz.exe: Opens the tool for transferring files and settings from Windows (for XP only)

·         SIDEBAR: Open the Windows (Vista only)

·         Sigverif : Opens the tool for verification of signatures of files

·         Winver : Opens the window for your Windows version

·         FSQUIRT: Bluetooth Transfer Wizard

·         IExpress opens the wizard for creating self-extracting archives. Tutorial HERE

·         MBLCTR: opens the mobility center (Windows Vista only)

·         MSRA : Opens Windows Remote Assistance

·         Mstsc : opens the tool connection Remote Desktop

·         MSDT: opens the diagnostic tools and support Microsoft

·         WERCON: opens the reporting tool and solutions to problems (for Vista only)

·         WINDOWSANYTIMEUPGRADE: enables the upgrade of Windows Vista

·         WINWORD : opens Word (if installed)

·         PRINTBRMUI : Opens migration wizard printer (Vista only)

Disk management

·         DISKMGMT.MSC: opens disk management utility

·         CLEANMGR: opens disk drive clean up utility

·         DFRG.MSC: opens disk defragmenter

·         CHKDSK: complete analysis of disk partition

·         DISKPART: disk partitioning tool

Connection management

·         IPCONFIG: lists the configuration of IP addresses on your PC (for more information type IPCONFIG/? in the CMD menu)

·         INETCPL.CPL: opens internet properties

·         FIREWALL.CPL: opens Windows firewall

·         NETSETUP.CPL: opens network set up wizard

Miscellaneous commands

·         JAVAWS: View the cover of Java software (if installed)

·         AC3FILTER.CPL: opens the properties AC3 Filter (if installed)

·         FIREFOX: Mozilla launches Firefox (if installed)

·         NETPROJ: allow or not connecting to a network projector (For Vista only)

·         LOGOFF: closes the current session

·         SHUTDOWN: shuts down Windows

·         SHUTDOWN-A: to interrupt Windows shutdown

·         %WINDIR% or %SYSTEMROOT%: opens the Windows installation

·         %PROGRAMFILES%: opens the folder where you installed other programs (Program Files)

·         %USERPROFILE%: opens the profile of the user currently logged

·         %HOMEDRIVE%: opens the browser on the partition or the operating system is installed

·         %HOMEPATH%: opens the currently logged user C:\Documents and Settings\ [username]

·         %TEMP%: opens the temporary folder

·         VSP1CLN: deletes the cache for installation of the service pack 1 for Vista

·         System File Checker (Requires Windows CD if the cache is not available):

·         SFC / scannow: immediately scans all system files and repairs damaged files

·         SFC / VERIFYONLY: scans only those files system

·         SFC / Scanfil = "name and file path": scans the specified file, and repairs if damaged

·         SFC / VERIFYFILE = "name and file path": Scans only the file specified

·         SFC / scanonce: scans the system files on the next restart

·         SFC / REVERT: return the initial configuration (For more information, type SFC /? In the command prompt CMD.

ORA-39083: Object type TYPE failed to create with error: ORA-02304: invalid object identifier literal

Error Description 

Import: Release 11.2.0.3.0 - Production on Thu Dec 26 13:48:26 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
;;;
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "CORP2012"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "CORP2012"."SYS_IMPORT_FULL_01":  CORP2012/******** directory=IMPDP dumpfile=26122013_1100-CORPORATE.DMP remap_schema= logfile= full=y
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"CORP2012" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."SPLIT_TBL"   OID 'ECD98FAC59A9469F8E458BDC2567F955' AS TABLE OF VARCHAR2 (32767)
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."MONTHWISESALES_OBJ_TYPE"   OID '8C344D8083BC496499E0FB3822C37F9F' IS OBJECT
(
ITEMNUMBER VARCHAR2(20),ITEM1  VARCHAR2(150),ITEMGROUP VARCHAR2(150),FMAXSALES NUMBER(15,2),
SMAXSALES NUMBER(15,2) ,THIRTYSALES NUMBER(15,2),JAN NUMBER(15,2),FEB NUMBER(15,2),MAR NUMBER(15,2),APR NUMBER(15,2),
MAY NUMBER(15,2),JUN NUMBER(15,2),JUL NUMBER(15,2),AUG NUMBER(15,2),SEP NUMBER(15
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."STOCKDTL_OBJ_TYPE"   OID '4E3C080CC3F94EB9947FEE8769738BD3' IS OBJECT
(
ITEMNUMBER VARCHAR2(20),ITEM1  VARCHAR2(150),ITEMGROUP VARCHAR2(150),PENDINGPR NUMBER(15,2),poqty number(15,2),
CLSTOCK NUMBER(15,2),PORTQTY NUMBER(15,2),ONWAY NUMBER(15,2)
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."BDFTREETYPE"   OID '9C2BA68B02FA4BFCBFD19561C64A3C2C' AS OBJECT (
PARENTNO NUMBER,
CHILDNO NUMBER,
SID NUMBER,
SC_CODE VARCHAR2 (500),
SD_CODE VARCHAR2 (500),
SRD_CODE VARCHAR2 (500),
NIIN_NO VARCHAR2 (100),
ITEMNAME VARCHAR2 (500),
WUC_CODE VARCHAR2 (100),
WUC_DESC VARCHAR2 (500),
SERIALNO VARCHAR2 (100),
DOCID VARCHAR2 (100),
TREEDESCRIPTION VARCHAR2 (1000),
APPCODE
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."SPLIT_TBL1"   OID 'DD944536D2EB453B8A965D8502B03C14' AS TABLE OF CLOB
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."FUNDFLOW_OBJ_TYPE"   OID '044C10C96FAD403FB31DBB9B72B02838' IS OBJECT
(
ACCOUNT VARCHAR2(100),INAMOUNT NUMBER(15,2),OUTAMOUNT NUMBER(15,2))
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."MONTHWISESALES_TABTYPE"   OID '260BF5B33A7D481CA814B61766ED47DA' AS TABLE OF MONTHWISESALES_OBJ_TYPE
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."STOCKDTL_TABTYPE"   OID '2DD34594CE534F01AC4E0E1EE3396186' AS TABLE OF STOCKDTL_OBJ_TYPE
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."BDFARRAYTYPE"   OID '9645FBF504544A508531FA40C217F950' AS TABLE OF BDFTREETYPE;
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "CORP2012"."FUNDFLOW_TABTYPE"   OID '4FA8101A71344FE5A3394AEB14D79F24' AS TABLE OF FUNDFLOW_OBJ_TYPE


Solution

CORP2012/******** directory=IMPDP dumpfile=26122013_1100-CORPORATE.DMP logfile=CORP2012_28122013.log REMAP_SCHEMA=CORPORATE:CORP2012 TABLE_EXISTS_ACTION=APPEND PARALLEL=5 TRANSFORM=oid:n 

How to increase no. of sessions in oracle database?

If you want to increase sessions parameter you should consider increasing processes and transactions parameter as well.

Here is the formula you can use to determine their values.

processes=x
sessions=x*1.1+5
transactions=sessions*1.1

E.g.
processes=500
sessions=555
transactions=610

Commands:-
sqlplus "/as sysdba"
or
sqlplus '/as sysdba'


sql> show parameter sessions
sql> show parameter processes
sql> show parameter transactions
sql> alter system set processes=500 SCOPE=SPFILE; 
sql> alter system set sessions=555 SCOPE=SPFILE; 
sql> alter system set transactions=610 SCOPE=SPFILE; 

and Restart the database.

Below parameters values also must be changed.....

sql>alter system set open_cursors=1500 scope=both;
sql>alter system set processes=3000 scope=spfile;
sql>alter system set job_queue_processes=4 scope=both;
sql>alter system set undo_retention=10800 scope=both;
sql>alter system set max_shared_servers=50 scope=both;
sql>alter system set db_files=2000 scope=spfile; 
sql>alter system set sessions=3305 SCOPE=SPFILE;  
sql>alter system set transactions=3635 SCOPE=SPFILE; 

ORA-00376: file 5 cannot be read at this time,ORA-01157: cannot identify/lock data file 5

Recovering the Database After the Loss of the SYSTEM or UNDO

Tablespace Datafile

In this case, we will just restore the tablespaces or datafiles that were lost. Of course,because these are critical tablespace objects, the database itself is down. After restoring the datafiles that were lost (do not restore any datafiles that are intact), recover the databasefollowing these steps:

1. Log into the database as SYS.

2. Mount the database with the startup mount command.

3. For recovery, you have two options. You can use the recover tablespace or the recoverdatafile command to recover the datafiles that were lost. It’s kind of up to you which one you want to use (we like the recover tablespace command in this situation more).

4. The recover database command will recommend to you the correct archived redo log to apply. At the prompt, type AUTO; the recover database command automatically starts applying all redo until the database is recovered.

5. Once database recovery is complete, the recover database command will return you to the  SQL prompt. You can then issue the alter database open command to open the database for business.

{

Recovery of the UNDO Tablespace

There are cases where the UNDO tablespace can be recovered online. If the database was shut down in a consistent manner before the UNDO tablespace was lost, it may be that all you will need to do is take the UNDO tablespace datafiles offline (you won’t be able to take the tablespace itself offline) and then open the database.Oracle has a default SYSTEM tablespace that would be used in this case, when the database initially comes up. You could then just create a new UNDO tablespace and drop the old one. This might be a quicker recovery method in some cases.

}

If the tablespace/datafile you lost is not associated with the SYSTEM or UNDO tablespaces,

then you are in luck. You don’t even need to shut down the database to recover! All you

need to do is take the datafiles offline, restore the impacted datafiles, recover the datafiles

(or the tablespace), and bring them back online.

The nice thing about this is if your users are not using the tablespace, they will never

know there was a problem. If the users are using the tablespace, they will be impacted only

if they try to use the datafiles that are offline (which is one good reason in some cases to

take just datafiles offline rather than the whole tablespace).

The first question is, How do you know which datafiles are missing? There are a couple

of things that will give you a clue. First of all, your users will start getting these messages:

SQL> select * from corporate.stockvalue;

select * from corporate.stockvalue

ERROR at line 1:

ORA-00376: file 5 cannot be read at this time

ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’

You can also look at the V$RECOVER_FILE view for more information on datafiles that

need recovery. Here is an example of such a query:

SQL> select * from v$recover_file;

FILE#     ONLINE                 ONLINE_               ERROR                                  CHANGE#            TIME

----------   -------                       -------                       --------------------                      ----------                  ---------

        5      ONLINE                 ONLINE                 FILE NOT FOUND                    0         

{

Missing Datafiles

Don’t expect that these errors indicating datafiles are missing will always show up in thealert log. Sometimes they will (for example, on database startup), but often they won’t (for example, when a query fails because a datafile is offline). If you want to monitor for this problem reliably, then the V$RECOVER_FILE view is the way to go.

}

So, here is the general recovery process from such an error. In this case we assume the

database is up and running:

1. Take the datafile offline using the alter database datafile offline command as

shown here:

alter database datafile ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’ offline;

As an alternative, you can use FILE_ID as shown in this example:

alter database datafile 5 offline;

FILE_ID will appear in the error message, or you can use the FILE_ID column of

DBA_DATA_FILES or the FILE# column in the V$DATAFILE view.

2. Restore the missing datafiles.

3. Restore all archived redo logs that will be needed for recovery. This would be all

archived redo logs generated from the beginning of the backup image you restored

in step 2.

Warning

When you are restoring backup files, never restore backed-up online redo

logs over the existing online redo logs. This is so important.we did not even back up the online redo logs. Restoring old online redo logs over your existing ones will lead to data loss. Fair warning!

4. Recover the missing datafiles with the recover datafile or recover tablespace command.

5. Bring the datafiles or the tablespace online with the alter database or alter tablespace ommand.So, what do you do if your database was down and you discover the files are lost when you start it up? That’s simple too.

1. Log in as SYS and start up the database. If a datafile is missing, you will get an error message that looks something like this:

SQL> startup

ORACLE instance started.

Total System Global Area 397557760 bytes

Fixed Size 1333452 bytes

Variable Size 289408820 bytes

Database Buffers 100663296 bytes

Redo Buffers 6152192 bytes

Database mounted.

ORA-01157: cannot identify/lock data file 5 - see DBWR trace file

ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’

2. It may be that you are missing more than datafile 4, since Oracle will alert you toonly the first datafile that it finds missing. Use the V$RECOVER_FILE, V$DATAFILE,and V$TABLESPACE views to determine exactly which datafiles are missing and which tablespaces they are associated with, as shown in this example:

SQL> select b.name ts_name, a.error, c.name datafile

2 from v$recover_file a, v$tablespace b, v$datafile c

3 where a.file#=c.file# and b.ts#=c.ts#

SQL> /

TS_NAME     ERROR                            DATAFILE

---------          --------------------                ------------------------------------

AXPERT       FILE NOT FOUND          D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF

3. Review the results of the query. As long as the missing datafiles are not part of the SYSTEM

or UNDO tablespace, you can simply take those datafiles offline and open the database. The

intent will be to recover those tablespaces/datafiles with the database open. First use the alter database datafile offline command to take the tablespaces offline:

SQL> alter database datafile ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’ offline;

Database altered.

4. Next, open the database with the alter database open command:

alter database open

5. Now restore the database backup datafiles from your hot backup media.

6. Restore all archived redo logs that will be needed for recovery. You will need to restore

all archived redo logs generated from the beginning of the backup image you restored in step 2.

Figuring Out Which Archived Redo Logs You Need

If you need to figure out exactly which archived redo logs you need to restore your backup (so, perhaps, you can restore those files off of backup media), you can use the V$RECOVER_FILE and the V$LOG_HISTORY views. The V$RECOVER_FILE view provides the last change number (in the CHANGE# column) present in the file(s) needing recovery. The V$LOG_HISTORY view will tell you which archived redo logs the changes are in. Here is an example:

ORA-01157: cannot identify/lock data file 5 - see DBWR trace file 

ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’

SQL> host copy AXPERT04.DBF.BKP AXPERT04.DBF

1 file(s) copied.

SQL> Select a.file#, a.change#, b.first_change#, b.next_change#, b.sequence#

2 From v$recover_file a, v$log_history b Where a.change#<=b.next_change#;

FILE#    CHANGE#            FIRST_CHANGE#             NEXT_CHANGE#              SEQUENCE#

---------- ----------                    -------------                               ------------                               ----------

5              1418889                1417349                                1438925                                20

7. Recover the datafiles or tablespaces using the recover datafile or recover tablespace command.

SQL> recover datafile 5;

8. Bring the datafiles or tablespaces online using the alter database datafile online or alter tablespace online command. Once you have done this, you have recovered the missing tablespace datafiles and your database is back to normal.

SQL>Alter database datafile 5 online;

Recovering the Database After the Loss of All Datafiles

Recovering the Database After the Loss of All Datafiles

You can use the recover database command to recover the entire database all at once.

Having restored all the database datafiles from the backup media, you would follow

these steps:

1. Log into the database as SYS.

2. Mount the database with the startup mount command.

3. Issue the recover database command from the SQL prompt.

4. The recover database command will recommend to you the correct archived redo log to apply. At the prompt,   type AUTO; the recover database command automatically starts applying all redo until the database is recovered.

5. Once database recovery is complete, the recover database command will return you to the SQL prompt. You can then issue the alter database open command to open the database for business.

1. Back up the database. Details on how to do a full online database backup are found in

2. In summary, follow these steps:

Ø  First put the database in hot backup mode.

Ø  Copy all database datafiles to a backup location.

Ø  Take the database out of hot backup mode.

Ø  Force a log switch. Back up the archived redo logs.

Here is an example of a backup:

C:\Users\Administrator>sqlplus

SQL*Plus: Release 11.2.0.3.0 Production on Fri Nov 22 14:14:31 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Enter user-name: sys@test as sysdba

Enter password:

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> alter database begin backup;

Database altered.

SQL> host copy D:\app\Administrator\oradata\TEST \*.dbf  E:\HOT_BACKUP

SQL> alter database end backup;

Database altered.

SQL> alter system switch logfile;

System altered.

SQL> host copy D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG\2013_10_31\*.ARC       E:\HOT_BACKUP\ARCHIVELOG

SQL> alter database backup controlfile to trace;

Database altered.

SQL> alter database backup controlfile to ‘E:\HOT_BACKUP\control1.bak’;

Database altered.

3. Now remove all datafiles from the database. On some operating-system platforms (Linux, for example), you can do this with the database up and running, and on others (Windows) you will have to shut down the database.

SQL> shut immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

5. Once you are sure the database is down, move old datafiles to some other location abd restore the database datafiles from their  backup location to the location where the database files belong.

6. Now connect to the database and issue the startup mount command.

C:\Users\Administrator>sqlplus

SQL*Plus: Release 11.2.0.3.0 Production on Fri Nov 22 14:14:31 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Enter user-name: sys@test as sysdba

Enter password:

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area 1.1758E+10 bytes

Fixed Size                  2265896 bytes

Variable Size            8522829016 bytes

Database Buffers         3221225472 bytes

Redo Buffers               12099584 bytes

Database mounted.

7. To recover the database, issue the recover database command. The command may return a response that says “media recovery complete,” as shown here:

SQL> recover database;

You may also be prompted to apply archived redo logs. Simply enter AUTO at the prompt.

SQL> recover database;

ORA-00279: change 5071334 generated at 08/17/2008 15:35:51 needed for thread 1

ORA-00289: suggestion :

D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_5_4bk6onh8_.arcORA-00280:

change 5071334 for thread 1 is in sequence #5

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

auto

ORA-00279: change 5071583 generated at 08/17/2008

15:40:04 needed for thread 1

ORA-00289: suggestion :

D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_6_4bk76kwk_.arcORA-00280:

change 5071583 for thread 1 is in sequence #6

ORA-00279: change 5091960 generated at 08/17/2008

15:49:05 needed for thread 1

ORA-00289: suggestion :

D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_7_4bk9ksb4_.arcORA-00280:

change 5091960 for thread 1 is in sequence #7

ORA-00279: change 5112317 generated at 08/17/2008

16:29:13 needed for thread 1

ORA-00289: suggestion :

D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_8_4bk9p236_.arcORA-00280:

change 5112317 for thread 1 is in sequence #8

ORA-00279: change 5112647 generated at 08/17/2008

16:31:29 needed for thread 1

ORA-00289: suggestion :

D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_9_4bk9p2mz_.arcORA-00280:

change 5112647 for thread 1 is in sequence #9

Log applied.

Media recovery complete.

8. Oracle will apply the needed redo and then return you to the SQL prompt. Assuming no errors occur, you can now open the database with the alter database open command as shown here:

SQL> alter database open resetlogs;

Database altered.

ORA-1031 with password file authentication

Troubleshooting ORA-1031 with password file authentication

If a local or remote sysdba connection fails with ORA-01031 than consider following factors : 

1. The database parameter remote_login_passwordfile has to be set to either EXCLUSIVE or SHARED . 

SQL> ALTER SYSTEM SET REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE SCOPE=SPFILE;

restart the database for the change to take effect. 

2. A password file is created in $ORACLE_HOME/dbs with option " nosysdba=n " . In general the name of the file would be in the format orapw<SID> .
In case of uncertainity recreate the password file using the below syntax : 

$ > orapwd file=$ORACLE_HOME/dbs/orapw<sid> password=<password> force=y nosysdba=n

 restart the database . 

The path to the password file %ORACLE_HOME%\database\PWD%ORACLE_SID%.ORA on a Microsoft Windows machine.