0% found this document useful (0 votes)
42 views7 pages

Checking Your Current Release Number: Sysdba and Sysoper

Uploaded by

Vijay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views7 pages

Checking Your Current Release Number: Sysdba and Sysoper

Uploaded by

Vijay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

The following example for UNIX and Linux operating systems sets the SID for the

instance that you will connect to in Step 6: Connect to the Instance:


■ Bourne, Bash, or Korn shell:

ORACLE_SID=mynewdb
export ORACLE_SID
■ C shell:
setenv ORACLE_SID mynewdb

Example 1–1 Setting Environment Variables in UNIX (C Shell)


setenv ORACLE_SID orcl
setenv ORACLE_HOME /u01/app/oracle/product/11.2.0/db_1
setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:/usr/lib:/usr/dt/lib:/usr/openwin/lib:/usr/ccs/lib

Checking Your Current Release Number


SELECT * FROM PRODUCT_COMPONENT_VERSION;

SYSDBA and SYSOPER


The following operations are authorized by the SYSDBA and SYSOPER system privileges:

System Privilege Operations Authorized


SYSDBA ■ Perform STARTUP and SHUTDOWN operations
■ ALTER DATABASE: open, mount, back up, or change character set

■ CREATE DATABASE

■ DROP DATABASE

■ CREATE SPFILE

■ ALTER DATABASE ARCHIVELOG

■ ALTER DATABASE RECOVER

■ Includes the RESTRICTED SESSION privilege

Effectively, this system privilege allows a user to connect as user SYS.


SYSOPER ■ Perform STARTUP and SHUTDOWN operations
■ CREATE SPFILE

■ ALTER DATABASE OPEN/MOUNT/BACKUP

■ ALTER DATABASE ARCHIVELOG

■ ALTER DATABASE RECOVER (Complete recovery only. Any form of

incomplete recovery, such as UNTIL


TIME|CHANGE|CANCEL|CONTROLFILE requires connecting as
SYSDBA.)
■ Includes the RESTRICTED SESSION privilege

This privilege allows a user to perform basic operational tasks, but


without the ability to look at user data.

Preparing to Use Operating System Authentication


To enable operating system authentication of an administrative user:
1. Create an operating system account for the user.
2. Add the account to the OSDBA or OSOPER operating system defined groups.
Connecting Using Operating System Authentication
A user can be authenticated, enabled as an administrative user, and connected to a
local database by typing one of the following SQL*Plus commands:

Creating a Password File with ORAPWD


REMOTE_LOGIN_PASSWORDFILE

Oracle DBA Fresher >> Done Nagesh Chillarge


LINKS

How to Create Different Editions or Versions for Oracle


Objects? Its Advantages

[Link]

[Link]

[Link]

[Link]
installation-and-patching/patching/specific-patches/applying-patch-set-update-112023-(patch-
12419353).aspx

[Link]

[Link]

[Link]
oracle-vm-virtual-box/

[Link]

[Link]

[Link]

[Link]

[Link]
RMAN-Backup

[Link]

[Link]

[Link]

i have installed linux in virtual box then database .how i will open oracle enterprise
manager ???? 
Run your virtual os
export ORACLE_SID = dbname
Conn / as sysdba

If db is in idle state then write startup

Your will db will open

Now open another terminal 


Write emctl start dB console

There is one link just right click on it and open in Firefox

Daily Work of DBA:


1: Health check of the Database.
2: Viewing the Alert log file to analyze the ORA errors if any.
3: Tablespace Utilization.
4: Rebuilding of Indexes, if bulk load of data is inserted.
5: Viewing the temporary files, through the DBA_TEMP_FILES.
6: Database Growth Comparision.
7: User Management.
8: Backing up the archive log files.
9: Monitoring Backups.
10: Monitoring the log files, backups, database space usage and the use of system resources.
11: Exports/Imports
12: User Management
13: Monitoring Tablespace Segments
14: Monitoring Production Database Performance
15: Solving the ORA errors.
16: Take a COLD/RMAN backups at night time.
Weekly Work of DBA:
1: Growth of the Database.
2: Total full backup of the database through hot backup.
3: Taking logical backups, in case of physical backups failure.
4: Taking weekly Tablespace backup.
Monthly Work of DBA:
1: Index Rebuild.
2: Tablespace Reorganization.
Quarterly Work of DBA:
1: Patching
2: Database Reorganization
Common tasks. Not compulsory tasks.

Some of Oracle's real life messages.


Q. What if your Dad loses his car keys?
A. 'Parent keys not found!'
Q. What if your old girl friend spots you with your new one?
A. 'Duplicate value on index!'
Q. What if the golf ball doesn't get into the hole at all?
A. 'Value larger than specified precision!'
Q. What if you try to freak out with somebody else's girlfriend and being kicked out?
A. 'Insufficient privileges on the specified object!'
Q. What if you don't get any response from the girl next door?
A. 'No data found!' or ' Query caused no rows retrieved!'
Q. What if you get response from the girl next door and her Mom too?
A. 'SELECT INTO returns too many rows!'
Q. What if you dial a wrong number?
A. 'Invalid number' or ' Object doesn't exist!'
Q. What if you try to beat your own trumpet?
A. 'Object is found mutating!'
Q. What if you are too late to office and the boss catches you?
A. 'Discrete transaction failed!'
Q. What if you see 'theatre full' when you go to a movie?
A. 'Maximum number of users exceeded!'
Q. What if you don't get table in the lunch room?
A. 'System out of tablespace!'
Q. What if you need to go on a diet?
A. Invalid Body Size

Boot Process in Linux (Redhat Linux & CentOS 5&6)


Linux Boot Process:
Press the power button on your system, and after few moments you see the Linux login prompt.
Have you ever wondered what happens behind the scenes from the time you press the power
button until the Linux login prompt appears?
The following are the 6 high level stages of a typical Linux boot process.
1. BIOS
§ BIOS stands for Basic Input/Output System
§ Performs some system integrity checks
§ Searches, loads, and executes the boot loader program.
§ It looks for boot loader in floppy, cd-rom, or hard drive. You can press a key (typically F12 of
F2, but it depends on your system) during the BIOS startup to change the boot sequence.
§ Once the boot loader program is detected and loaded into the memory, BIOS gives the control
to it.
§ So, in simple terms BIOS loads and executes the MBR boot loader.
2. MBR
§ MBR stands for Master Boot Record.
§ It is located in the 1st sector of the bootable disk. Typically /dev/hda, or /dev/sda
§ MBR is less than 512 bytes in size.
§ It contains information about GRUB (or LILO in old systems).
§ So, in simple terms MBR loads and executes the GRUB boot loader.
3. GRUB
§ GRUB stands for Grand Unified Bootloader.
§ If you have multiple kernel images installed on your system, you can choose which one to be
executed.
§ GRUB displays a splash screen, waits for few seconds, if you don’t enter anything, it loads the
default kernel image as specified in the grub configuration file.
§ GRUB has the knowledge of the filesystem (the older Linux loader LILO didn’t understand
filesystem).
§ Grub configuration file is /boot/grub/[Link] (/etc/[Link] is a link to this). The following is
sample [Link] of CentOS.
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/[Link]
hiddenmenu
title CentOS (2.6.18-194.el5PAE)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-194.el5PAE ro root=LABEL=/
initrd /boot/[Link]
§ As you notice from the above info, it contains kernel and initrd image.
§ So, in simple terms GRUB just loads and executes Kernel and initrd images.
4. Init
§ Looks at the /etc/inittab file to decide the Linux run level.
§ Following are the available run levels
§ 0 – halt
§ 1 – Single user mode
§ 2 – Multiuser, without NFS
§ 3 – Full multiuser mode
§ 4 – unused
§ 5 – X11
§ 6 – reboot
§ Init identifies the default initlevel from /etc/inittab and uses that to load all appropriate program.
§ Execute ‘grep initdefault /etc/inittab’ on your system to identify the default run level
§ If you want to get into trouble, you can set the default run level to 0 or 6. Since you know what
0 and 6 means, probably you might not do that.
§ Typically you would set the default run level to either 3 or 5.
5. Runlevel programs
§ When the Linux system is booting up, you might see various services getting started. For
example, it might say “starting sendmail …. OK”. Those are the runlevel programs, executed
from the run level directory as defined by your run level.
§ Depending on your default init level setting, the system will execute the programs from one of
the following directories.
§ Run level 0 – /etc/rc.d/rc0.d/
§ Run level 1 – /etc/rc.d/rc1.d/
§ Run level 2 – /etc/rc.d/rc2.d/
§ Run level 3 – /etc/rc.d/rc3.d/
§ Run level 4 – /etc/rc.d/rc4.d/
§ Run level 5 – /etc/rc.d/rc5.d/
§ Run level 6 – /etc/rc.d/rc6.d/
§ Please note that there are also symbolic links available for these directory under /etc directly.
So, /etc/rc0.d is linked to /etc/rc.d/rc0.d.
§ Under the /etc/rc.d/rc*.d/ directories, you would see programs that start with S and K.
§ Programs starts with S are used during startup. S for startup.
§ Programs starts with K are used during shutdown. K for kill.
§ There are numbers right next to S and K in the program names. Those are the sequence
number in which the programs should be started or killed.
§ For example, S12syslog is to start the syslog deamon, which has the sequence number of 12.
S80sendmail is to start the sendmail daemon, which has the sequence number of 80. So, syslog
program will be started before sendmail.
There you have it. That is what happens during the Linux boot process

>> What is role of [Link], [Link], and [Link] file?


can I start my databse without these files?

<<These files only deals with network connectivity,hence database can be started without these files

You might also like