Thursday, July 3, 2008

Startup nomount

- Read the Parameter file and start the instance (allocate memory/SGA and start background processes)

- NOTE: SELECT STATUS FROM V$INSTANCE; this will show a status of STARTED

Startup mount

- Read the Parameter file and start the instance (allocate memory/SGA and start background processes)

- Read the controlfile(s)

- NOTE: SELECT STATUS FROM V$INSTANCE; this will show a status of MOUNTED

Status = OPEN means the database is open and available.

Instance Modes:

SHUTDOWN

- Only superuser can connect

- This is where you issue STARTUP command

- Instance is down, V$INSTANCE is not available

NOMOUNT

-- Only superuser can connect

-- Parameter file is read and the Instance started (memory/SGA allocated and background processes started)

-- SELECT status FROM v$instance; will show STARTED

-- from here you can issue:

- CREATE DATABASE (if database does not exist)

- CREATE CONTROLFILE (if you are recreating a controlfile)

- ALTER DATABASE MOUNT (if you want to go into MOUNT MODE) MOUNT

-- Only superuser can connect

-- This is when all the control files are read and verified to be to same

-- SELECT status FROM v$instance; will show MOUNTED

-- In order to get into mount mode, it will go into nomount mode first

-- from here you can issue:

- RECOVER commands (if you are performing closed db recovery)

- ALTER DATABASE ARCHIVELOG/NOARCHIVELOG;

- ALTER DATABASE OPEN; (to make datatabase available to regular

users)

- SHUTDOWN (if you want to close the instance) OPEN

-- Any user with CREATE SESSION privilege can now connect

-- User data is now available

-- Before the db actually opens, Oracle will check all the datafiles and redo logs to make sure they are in sync

-- SELECT status FROM v$instance; will show OPEN

-- In order to get into open mode, it will go into nomount mode first and then mount mode.

The only reason you STARTUP NOMOUNT or STARTUP MOUNT is if you have work to do, such as creating the database or recovering the database. If no work, people generally just do STARTUP which will start the instance (nomount

mode) then read the controlfiles (mount mode) and then read the datafiles (open).

DBA FQA's

The interview process can be quite stressful. Here is the first part of a two part series on helping you answer those tough questions that you might experience in your quest for an Oracle DBA position. I actually wrote this article a long time ago but it is amazing how many questions I still get every week from this one. Stay tunned for Part II next week. Technical - Oracle This is the part you have all been waiting on. Please if you have just skipped to this section, go back to the personal section and read it. There is much to be gained by the personal section and conveying to your interviewer who you are and how you tick from day to day. Also, the answers I am giving here are off the cuff and are not intended to be the definitive answer to these questions. There are many aspects to these questions that just cannot be answered here and honestly, you will not have time to explain any of these questions fully in the interview process. It is up to you to make sure your interviewer understands that you understand the question and have given enough information that they know you understand the concept.

1. Explain the difference between a hot backup and a cold backup and the benefits associated with each.

A hot backup is basically taking a backup of the database while it is still up and running and it must be in archive log mode. A cold backup is taking a backup of the database while it is shut down and does not require being in archive log mode. The benefit of taking a hot backup is that the database is still available for use while the backup is occurring and you can recover the database to any point in time. The benefit of taking a cold backup is that it is typically easier to administer the backup and recovery process. In addition, since you are taking cold backups the database does not require being in archive log mode and thus there will be a slight performance gain as the database is not cutting archive logs to disk.

2. You have just had to restore from backup and do not have any control files. How would you go about bringing up this database?

I would create a text based backup control file, stipulating where on disk all the data files where and then issue the recover command with the using backup control file clause.

3. How do you switch from an init.ora file to a spfile?

Issue the create spfile from pfile command.

4. Explain the difference between a data block, an extent and a segment. A data block is the smallest unit of logical storage for a database object. As objects grow they take chunks of additional storage that are composed of contiguous data blocks. These groupings of contiguous data blocks are called extents. All the extents that an object takes when grouped together are considered the segment of the database object.

5. Give two examples of how you might determine the structure of the table DEPT. Use the describe command or use the dbms_metadata.get_ddl package.

6. Where would you look for errors from the database engine? In the alert log.

7. Compare and contrast TRUNCATE and DELETE for a table. Both the truncate and delete command have the desired outcome of getting rid of all the rows in a table. The difference between the two is that the truncate command is a DDL operation and just moves the high water mark and produces a now rollback. The delete command, on the other hand, is a DML operation, which will produce a rollback and thus take longer to complete.

8. Give the reasoning behind using an index. Faster access to data blocks in a table.

9. Give the two types of tables involved in producing a star schema and the type of data they hold. Fact tables and dimension tables. A fact table contains measurements while dimension tables will contain data that will help describe the fact tables.

10. . What type of index should you use on a fact table? A Bitmap index.

11. Give two examples of referential integrity constraints. A primary key and a foreign key.

12. A table is classified as a parent table and you want to drop and re-create it. How would you do this without affecting the children tables? Disable the foreign key constraint to the parent, drop the table, re-create the table, enable the foreign key constraint.

13. Explain the difference between ARCHIVELOG mode and NOARCHIVELOG mode and the benefits and disadvantages to each. ARCHIVELOG mode is a mode that you can put the database in for creating a backup of all transactions that have occurred in the database so that you can recover to any point in time. NOARCHIVELOG mode is basically the absence of ARCHIVELOG mode and has the disadvantage of not being able to recover to any point in time. NOARCHIVELOG mode does have the advantage of not having to write transactions to an archive log and thus increases the performance of the database slightly.

14. What command would you use to create a backup control file? Alter database backup control file to trace.

15. Give the stages of instance startup to a usable state where normal users may access it. STARTUP NOMOUNT - Instance startup STARTUP MOUNT - The database is mounted STARTUP OPEN - The database is opened

16. What column differentiates the V$ views to the GV$ views and how? The INST_ID column which indicates the instance in a RAC environment the information came from.

17. How would you go about generating an EXPLAIN plan? Create a plan table with utlxplan.sql. Use the explain plan set statement_id = 'tst1' into plan_table for a SQL statement Look at the explain plan with utlxplp.sql or utlxpls.sql

18. How would you go about increasing the buffer cache hit ratio? Use the buffer cache advisory over a given workload and then query the v$db_cache_advice table. If a change was necessary then I would use the alter system set db_cache_size command.

19. Explain an ORA-01555 You get this error when you get a snapshot too old within rollback. It can usually be solved by increasing the undo retention or increasing the size of rollbacks. You should also look at the logic involved in the application getting the error message.

20. Explain the difference between $ORACLE_HOME and $ORACLE_BASE. ORACLE_BASE is the root directory for oracle. ORACLE_HOME located beneath ORACLE_BASE is where the oracle products reside. Well, we have gone through the first 25 questions as I would answer them during an interview. Please feel free to add your personal experiences to the answers as it will always improve the process and add your particular touch. As always remember these are "core" DBA questions and not necessarily related to the Oracle options that you may encounter in some interviews. Take a close look at the requirements for any job and try to come up with questions that the interviewer may ask. Next time we will tackle the rest of the questions. Until then, good luck with the process.

21. How would you determine the time zone under which a database was operating? select DBTIMEZONE from dual;

22. Explain the use of setting GLOBAL_NAMES equal to TRUE. Setting GLOBAL_NAMES dictates how you might connect to a database. This variable is either TRUE or FALSE and if it is set to TRUE it enforces database links to have the same name as the remote database to which they are linking.

23 What command would you use to encrypt a PL/SQL application?

WRAP

24. Explain the difference between a FUNCTION, PROCEDURE and PACKAGE.

A function and procedure are the same in that they are intended to be a collection of PL/SQL code that carries a single task. While a procedure does not have to return any values to the calling application, a function will return a single value. A package on the other hand is a collection of functions and procedures that are grouped together based on their commonality to a business function or application.

1.Functions are restricted to returning a single value, Stored procedures can have multiple output parameters.

2. Functions can be call from SQL Statements, procedures are called from the application, stored procedur is only compiled once after that it stays in the momery as long as you dont shutdown the database. this is a performance boost.

3. Stoed procedure accepts insert update delete and select while function only accept select statment.

25 Explain the use of table functions. Table functions are designed to return a set of rows through PL/SQL logic but are intended to be used as a normal table or view in a SQL statement. They are also used to pipeline information in an ETL process.

26. Name three advisory statistics you can collect. Buffer Cache Advice, Segment Level Statistics, & Timed Statistics

27. Where in the Oracle directory tree structure are audit traces placed? In unix $ORACLE_HOME/rdbms/audit, in Windows the event viewer

28. Explain materialized views and how they are used. Materialized views are objects that are reduced sets of information that have been summarized, grouped, or aggregated from base tables. They are typically used in data warehouse or decision support systems.

29. When a user process fails, what background process cleans up after it? PMON

30. What background process refreshes materialized views? The Job Queue Processes.

31. How would you determine what sessions are connected and what resources they are waiting for? Use of V$SESSION and V$SESSION_WAIT

32. Describe what redo logs are. Redo logs are logical and physical structures that are designed to hold all the changes made to a database and are intended to aid in the recovery of a database.

33. How would you force a log switch? ALTER SYSTEM SWITCH LOGFILE;

34. Give two methods you could use to determine what DDL changes have been made. You could use Logminer or Streams

35. What does coalescing a tablespace do? Coalescing is only valid for dictionary-managed tablespaces and de-fragments space by combining neighboring free extents into large single extents.

36. What is the difference between a TEMPORARY tablespace and a PERMANENT tablespace? A temporary tablespace is used for temporary objects such as sort structures while permanent tablespaces are used to store those objects meant to be used as the true objects of the database.

37. Name a tablespace automatically created when you create a database. The SYSTEM tablespace.

38. When creating a user, what permissions must you grant to allow them to connect to the database? Grant the CONNECT to the user.

39. How do you add a data file to a tablespace? ALTER TABLESPACE ADD DATAFILE SIZE

40. How do you resize a data file? ALTER DATABASE DATAFILE RESIZE ;

41. What view would you use to look at the size of a data file? DBA_DATA_FILES

42. What view would you use to determine free space in a tablespace? DBA_FREE_SPACE

43. How would you determine who has added a row to a table? Turn on fine grain auditing for the table.

44. How can you rebuild an index? ALTER INDEX REBUILD;

45. Explain what partitioning is and what its benefit is. Partitioning is a method of taking large tables and indexes and splitting them into smaller, more manageable pieces.

46. You have just compiled a PL/SQL package but got errors, how would you view the errors? SHOW ERRORS 47. How can you gather statistics on a table? The ANALYZE command.

48. How can you enable a trace for a session? Use the DBMS_SESSION.SET_SQL_TRACE or Use ALTER SESSION SET SQL_TRACE = TRUE;

49. What is the difference between the SQL*Loader and IMPORT utilities? These two Oracle utilities are used for loading data into the database. The difference is that the import utility relies on the data being produced by another Oracle utility EXPORT while the SQL*Loader utility allows data to be loaded that has been produced by other utilities from different data sources just so long as it conforms to ASCII formatted or delimited files.

50. Name two files used for network connection to a database. TNSNAMES.ORA and SQLNET.ORA

Thursday, June 12, 2008

For Checking any uncommitted transaction

 

 

 

you have to look in V$TRANSACTION, where used_ublk > 0. You can see start_time.

 

 

desc v$transaction;

 Name                                                  Null?    Type

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

 ADDR                                                           RAW(4)

 XIDUSN                                                         NUMBER

 XIDSLOT                                                        NUMBER

 XIDSQN                                                         NUMBER

 UBAFIL                                                         NUMBER

 UBABLK                                                         NUMBER

 UBASQN                                                         NUMBER

 UBAREC                                                         NUMBER

 STATUS                                                         VARCHAR2(16)

 START_TIME                                                     VARCHAR2(20)

 START_SCNB                                                     NUMBER

 START_SCNW                                                     NUMBER

 START_UEXT                                                     NUMBER

 START_UBAFIL                                                   NUMBER

 START_UBABLK                                                   NUMBER

 START_UBASQN                                                   NUMBER

 START_UBAREC                                                   NUMBER

 SES_ADDR                                                       RAW(4)

 FLAG                                                           NUMBER

 SPACE                                                          VARCHAR2(3)

 RECURSIVE                                                      VARCHAR2(3)

 NOUNDO                                                         VARCHAR2(3)

 PTX                                                            VARCHAR2(3)

 NAME                                                           VARCHAR2(256)

 PRV_XIDUSN                                                     NUMBER

 PRV_XIDSLT                                                     NUMBER

 PRV_XIDSQN                                                     NUMBER

 PTX_XIDUSN                                                     NUMBER

 PTX_XIDSLT                                                     NUMBER

 PTX_XIDSQN                                                     NUMBER

 DSCN-B                                                         NUMBER

 DSCN-W                                                         NUMBER

 USED_UBLK                                                      NUMBER

 USED_UREC                                                      NUMBER

 LOG_IO                                                         NUMBER

 PHY_IO                                                         NUMBER

 CR_GET                                                         NUMBER

 CR_CHANGE                                                      NUMBER

 

Monday, June 2, 2008

Temp files and tablespaces

FOR DBA

Where are my TEMPFILES, I don't see them in V$DATAFILE or DBA_DATA_FILE?

Tempfiles, unlike normal datafiles are not listed in v$datafile or dba_data_files. Instead query v$tempfile or dba_temp_files:

SELECT * FROM v$tempfile;

SELECT * FROM dba_temp_files;

How do I find used/free space in a TEMPORARY tablespace?

Unlike normal tablespaces, true temporary tablespace information is not listed in DBA_FREE_SPACE. Instead use the V$TEMP_SPACE_HEADER view:

SELECT tablespace_name, SUM (bytes used), SUM (bytes free)

FROM V$temp_space_header

GROUP BY tablespace_name;

Friday, May 30, 2008

Library cache

 
The library cache stores shared SQL, caching the parse tree and the execution plan for every unique SQL statement.

If multiple applications issue the same SQL statement, each application can access the shared SQL area. This reduces the amount of memory needed and reduces the processing-time used for parsing and execution planning.





take  care

With All My Luv

VISHAL......


CEAT

SGA (System Global Area)

Each Oracle instance uses a System Global Area or SGA — a shared-memory area — to store its data and control-information. [5]

Each Oracle instance allocates itself an SGA when it starts and de-allocates it at shut-down time. The information in the SGA consists of the following elements, each of which has a fixed size, established at instance startup:

*                   the database buffer cache: this stores the most recently-used data blocks. These blocks can contain modified data not yet written to disk (sometimes known as "dirty blocks"), unmodified blocks, or blocks written to disk since modification (sometimes known as clean blocks). Because the buffer cache keeps blocks based on a most-recently-used algorithm, the most active buffers stay in memory to reduce I/O and to improve performance.

*                   the redo log buffer: this stores redo entries — a log of changes made to the database. The instance writes redo log buffers to the redo log as quickly and efficiently as possible. The redo log aids in instance recovery in the event of a system failure.

*                   the shared pool: this area of the SGA stores shared-memory structures such as shared SQL areas in the library cache and internal information in the data dictionary. An insufficient amount of memory allocated to the shared pool can cause performance degradation.

 

 

Oracle DBA tips