1) how can you tune your data base?

There are so many areas where a DBA need to concentrate to tune the database. Fe w of these areas are dependent of each other. So we need to very careful regardi ng side effect of one side tuning to other. As a thumb rule, we generally apply the DAMICO method to tune our database. That is design of the database, tuning the application(sql tuning), memory tuning, I/O tuning, contention tuning and OS tuning. 2) what will you do if you get a complain your database is slow? If we get a complaint regarding database slowness, first of all we need to ensur e whether the issue is user specific, module specific or on entire application l evel. In order to understand better problem, you should ask questions to yoursel f or person encountering performance issue like 1. Is whole application slow or only component of the application is slow? ( like only concurrent manager running slow) 2. Is this a particular component like report server slow then is a particu lar report or all reports are slow? 3. Is performance issue during all time or at specific time let’s say from 11 AM to 4PM? 4. Was performance issue popped up recently or performance degradation is s ince long? 5. What changed recently? Depending on answer you can start looking into application like if issue is user specific, module specific or on entire application level. If it is user specific problem, trace the user session and find the root cause o f the problems and area where database is performing poorly, and either tune (if possible) or kill the session. At broad level, we need to focus on these areas and to find the root cause of the problems. 1. Is gather stats schedule (atleast weekly?)? 2. Is Purge Obsolete Workflow request & concurrent request purging schedule d? 3. Is there any runaway process on database tier or application tier? (Runa way process is process taking unexceptionally long time with high CPU or memory usage) 4. Any discoverer process taking long time or high CPU? (usually on Middle tier like dis4ws..) 5. Any custom report taking long time? 3) what is the diff between lock and deadlock? A lock enables multiple users to access the database concurrently. When a user m odify the database record, a lock is applied on that record and it prevents othe r users to write to database. Depending on the various modification tasks, a loc k can be classified into three categories: exclusive lock, shared lock and updat e lock. Whereas a deadlock is a situation where two or more transactions are put into wait state simultaneously, each transaction acquires a lock that prevents other transaction to write until it get released.and in this situation, each wai ts for the other transaction to get released. Whenever we get a deadlock situati on, in the alert log file, we can see ORA-00060 error. We need to trace the sess ion experiencing the deadlock and take the appropriate action to kill one sessio n. 4) Explain what and how is your database architecture designed ( nodes) 5) what is the diff workflow and concrent request. Business processes revolve around routing information through various users thro ugh set of constantly changing rules. The flow of information is governed by var ious conditions and checking for outcome of previous steps. An established proce ss of routing will be subject to continuous monitoring and rounting. Each organi

Workflow can route supporting informat ion to each decision maker in a business process. When a user runs a report. and is uniquely identified by a request ID. RMAN-05501 Getting this when creating standby database RMAN-06002: command not allowed when not connected to a recovery catalog 10) Error in patching and how to rectify patch failure issue in database Unable to copy the files: adpatch fails when it does not find space to copy all . 7) how can you check your serves details.zation follows a different set of business practices. It’s naming convention is either <CONTEXT_NAME>. device type: SBT_TAPE. RMAN fails with ORA-01031 (insufficient privileges) or ORA-01017 (invalid userna me/password) errors when trying to connect to the target database RMAN-10003: unable to connect to target database using connect string system/man ager@proddb" RMAN-04004: error from recovery catalog database: ORA-28009: connection as SYS s hould be as SYSDBA or SYSOPER RMAN-20202: Tablespace not found in the recovery catalog RMAN-03009: failure of backup command on ch2 channel at 11/07/2011 17:37:00 ORA-19504: failed to create file "/PDF/AMDD_BACKUP/AMDD_Lvl0_Hot_Back" ORA-27038: created file already exists RMAN-03009: failure of allocate command on t1 channel at 07/21/2005 13:49:06 ORA-19554: error allocating device. how many instance. When we run autoconfig. Concurrent programs are started by a concurrent manag er. 9) Error in RMAN backup and recovery. Oracle application context file is an xml file which is a central repository to store configuration parameters of oracle applications. 6) what is the diff be env file and xml file.env is called consolidated environment file beca use it sources both technology stack and applications.dbf RMAN-06012: channel: C2 not allocated RMAN-06023: no backup or copy of datafile 4 found to restore RMAN-06059: expected archived log not found. ho w many servers .Workflow gets the right inf ormation to the right people. how many threads. a request to run the report is generated. lost of archived log compromises recoverability RMAN-05001: auxiliary file name conflicts with a file used by the target databas e . technology stack an d applications. device name: ORA-27211: Failed to load Media Management Library RMAN-03009: failure of backup command on ch00 channel at 02/04/2010 23:34:43 ORA-19566: exceeded limit of 0 corrupt blocks for file /db/FINPRODDATA/oradata/p sindex. There are different types of environment files in oracle appli cations which are used to source database tier.env or APPS<CONTEX T_NAME>. their request is inserted into a database table. Workflow lets you provide each person with all the information they need to take an action. The program that generates the repor t is a concurrent program. 8) steps of backup (RMAN) and recovery. Every time your users request a concurrent program to be run. C oncurrent managers read requests from this table. APPS<CONTEXT_NAME>.env. http server. Oracle Applications Environment Files are the files which are used to source the system directly. e ach product’s template file use the context file to populated and create new confi guration file. The command to run the report is a concurrent request. including how many nodes are there.

you will find a file called libc. it’s servlet mode Report Server . . This happens because applsys ac count get locked. noautoconfig. copy the location of the sql file and run the sql file manually.txt located at $APPL_TOP/admin should have correct digital sig nature. hidepasswd only these are used to run adpatch. Although apps password is correctly given adpatch fails. If the sql file successfully executes. . Compilation of jsp files is failing Resolution: manually complile the jsp files using ojspcompile. Failure of . Odf file fails Resolution: existing object may be present or unable to run sql statements. Issue with adjava Resolution: you need to ensure that the classpath environment variable is proper ly set and adsign.the files in the product_top. Resolution: applprod.ldt files Resolution: run the .fmb code to see which procedure is being coded in the form.pl. nocompilejsp. Resolution: add space to product_top and restart the patch Adpatch is failing during pre-req checks Resolution: this will happen because adsnapshot has been not properly upgraded. In this location. Go t o log file. Failure of . 11) Difference between R11 and R12 ? Plugin for forms 11i uses JInitiator as the default plugin R12 replaces JInitiator with Sun Java Plugin Forms Mode Default mode in 11i is socket mode In R12. this file should always point to current instance.wft file manually using WFLOAD. Adpatch is erroring out stating missing product.rdf code to see which procedure is being called in the form .wft files Resolution: run .rdf is failed to regenerate Resolution: see the . in this situat ion.pls files Resolution: execute it manually otherwise troubleshoot it based on error. Possib le reasons are lack of permissions or additional procedures. c) Relinking of executable files is failed Resolution: go to $ORACLE_HOME/lib/stubs.ldt file manually using FNDLOAD. go to adctrl and skip the worker. go and compile the procedure manually. we have two options a) stop the adpatch.so. Go and compile the procedure manually. once the utility completes. restart the adpatch b) go to adadmin and maintain snapshot information or apply the patch with noprereq option.txt will have all the information of product tops.fmx is failed to regenerate Resolution: see the . So you need to unlock the applsys account. In this case. Failure of .

3.1. appache . 12) AWR report 13) health check up? 14) Define and Issues related with with concurrent manager and workflow? 15) What is the diff between different type of concurrent request? 16) if a worker fails repetitively .g.6 ORACLE_HOME R12.   . in this situation.ORACLE AS10g 10. we need to load the jar files manually using loadjava command.1. Stop the forms and check for forms processes if you find any kill them.3.1.7) R12. it should not be greater than 2gb 23) where are the configuration file located and how to amend ( conc.1. e. loadjava –user apps/apps –v –force –resolve <JAR FILE PATH> 18) steps of patching and cloning in oracle apps.ORACLE AS10g 10.6i R12.19 R12.1. including multinode.5 for web and concurrent processing Servlet container 11i.OC4J ORACLE_HOME 11i. Verify the size of the log files. some jar files are not loaded by adadmin.8. what will you do? 17) Issue related regenerating jar files Sometimes.0.x | Proxies and deselect Use Browser Sett ings and enter the details for the proxy settings. dicoverer) 24) location of log files 25) issues with users regarding the forms FRM-92010 Cause: This error can occur when JInitiator uses the browser s proxy setting.2 11i. Solution: Go to Control Panel | JInitiator 1.31 Forms Version 11i.3 R12 introduces INST_TOP which contains the startup-shutdown scripts.IAS_ORACLE_HOME (8.10g JDK Version R12 uses JDK 1.3.Jserv R12. 19) Error occurred after patching and cloning? 20) relink? 21) what do you mean by begin backup mode and end backup mode ? 22) difference between putting database in begin backup mode and stopping the se rvices ? 23) issues with forms server Form server is not coming up or hanging Stop the forms and check whether the forms port is avaliable or occupied by any process by using netstat command.x. form. configurati on and log files. FRM-92050 ■ Heavy load on the server. before starting the forms makesure that there are no forms processes running specific t o that instance..No report server in R12 Apache Version 11i.

dll Cause: The Forms Web executable frmweb. which loads the applet. FRM-92100 Cause: This error occurs if the Web server is shutdown when the user is accessing the a pplication Solution: Check if the Web server is up and running. ■ Incorrect Use of RUN_PRODUCT Cause: RUN_PRODUCT should only be used. then it indicates that the Web server is down. Set the PATH environment variable in formsweb.dll is located in a directory specified in the PATH environment variable. ■ Make sure that the value of the ServerArgs is not null. This main ly depends on the server computer performance and configuration.env. in the configuration fil e (formsweb. Solution: ■ The Forms Runtime Prestart feature of Oracle Application Server Forms Services 1 0g comes in handy in this situation.dll Solution: Ensure that jvm. for integration with Oracle Gr aphics 6i. which is typically ORACLE_HOME/forms/server/default. Solution: RUN_PRODUCT Built-in calls that are used to integrate Oracle Forms with Oracle R eports should be replaced using the newer RUN_REPORT_OBJECT Built-in. ■ Missing jvm. and avoiding applicati on or server hangs because of a rush.dll. used to load the forms applet. If the OC4J home page does not come up. ■ Upgrade the hardware of the server computer to handle the high number of simulta neous requests.env) and the registry for the FORMS_TIMEOUT parameter value. These parameters can be defined in the Oracle Forms c onfiguration file (formsweb. for example: FORMS_TIMEOUT="10" This is an incorrect entry.cfg. ■ Wrong FORMS_TIMEOUT Cause: The value of FORMS_TIMEOUT parameter is entered wrongly. the Form name is required in ServerArgs. Solution: ■ Make sure that the HTML file. The value should not be in quotes. This feature pre-spawns a configurable numb er of runtime engines to handle incoming client requests. has the ServerArgs parameter in it.cfg) Solution: Edit the forms configuration file to enter a valid serverURL parameter value. to point to the location of the jvm.Cause: If there are many simultaneous requests that the server cannot handle. ■ Missing ServerArgs parameter Cause: The ServerArgs parameter is missing from the HTML. FRM-92101 . Try the URL http://servercomputer:por tno. ■ Missing serverURL Parameter Cause: The serverURL parameter is either missing or incorrect. FORMS_TIMEOUT=10 This is the correct entry. Remember. in Oracle Forms.exe is not able to find the jvm.cfg) or can be directly passed in the URL that is us ed to run the Form. Solution: Verify the environment file (default. Contact your Forms or server administr ator to start the Web server. The value should be a proper integer.

FRM-92102 Cause: This error can occur because of the network problems between the Web server and the client.com:NNNN in your browser. Here you need to replace myse rver.log file can be found in the application-deployments/formsapp directory of the OC4J instance on which Oracle Forms is deployed. then. Solution: ■ This can be confirmed by looking for a log message like “Unable to switch to Worki ng Directory:<workingDirectory>” in the application. I t is then. FRM-92150/FRM-92160 Cause: Wrong path and/or codebase setting. then your HTTP server is down and you need to contact your system administrator to bring it up. FRM-92120 Cause: This is a server configuration error. which occurs when the client is unable to find the file Registry. make sure that the value of heartbeat is less than that of FORMS_TIMEOUT.com:NNNN your browser will show the “OracleAS welcome”. Solution: When this error occurs. there is a possibility that the HTTP server has gone down.com with your host name and NNNN with your HTTP server’s port number. ■ FORMS_TIMEOUT and heartbeat Cause: This error can occur if the forms applet parameter ‘heartbeat’ is set to a value mor e than FORMS_TIMEOUT. If that is not desired for a particular a pplication. networkRetries=30 This parameter specifies the number of times the Forms c lient should try reconnecting to the middle tier before finally timing out. if you suddenly come across this error. The CODEBASE entry in your HTML file or forms configuration file may point to older versions .■ Wrong working directory Cause: This error can occur if the working directory specified does not exist. Removing the blocks on the ports on the Web server solves the error. If your browser says that it could not connect to the server. it could be due to the ports on the web server restricted at TCP/IP level.dat on the middle tier. When the HTTP server is up and running. In a running Forms application. on giving the URL http://myserver. heartbeat is set to a value higher than that of FORMS_TIMEOUT. ■ Ports Blocked Cause: If the error occurs even after setting up an appropriate value for networkRetrie s. You may verify this by typing the URL http://myserver. only w hen the application is desired to time-out after a certain time of inactivity. Set the value to a suitable number according to the network characteristics and needs. The client is not able to communicate with the server on the specifi ed port. for exa mple. then it needs to be placed. If it is not present. you would get a FRM -92120. Solution: A socket connection requires a port at each end. Edit the forms configuration file with the corre ct working directory.dat is present on the middle tier in the directory ORACLE_HOME/forms/java/oracle/forms/registry. If the port is closed it causes the communication stoppage. The application. check if the file Registry. Firewall and proxies are used to protect the ports. Solution: Add the parameter networkRetries to the forms configuration file. Solution: Set the proper ORACLE_HOME/bin in the beginning of the system path.log file. Solution: Generally.

or the repository could not be located or reached. If you are connecting from a login dialog box.. or it may indicate tha t the server has gone down. When using the local naming method.directory_path paramete r in the sqlnet. then use the adapters command to determine which adapters are in use. Action: Perform the following steps: 1. ensure that the name given in the connect string is correct and complete. Verify the ldap. An unexpected end of file wa s processed on the communication channel. 2. If none are configured. If the net se rvice name in the connect string is simple. then verify that you are not p lacing an at sign (@) before your connect net service name.You may need to modify your retransmission count.ora f ile exactly if the name is simple and there is not NAMES_DEFAULT_DOMAIN in the s qlnet. then check the NAMES_DEFAULT_DIRECTO RY parameter in the sqlnet. Installed Oracle Net naming methods are: Local Naming (tnsnames. For example . do the following: 1. This may be an indication that the com munications link may have gone down at least temporarily.ora file. Activate client tracing and repeat the operation.log file on the server. Verify there is an entry in the tnsnames. Verify that the tnsnames. Check the resolution path for each adapter for possible problems.ora file for the name given in the c onnect string. The following directories are searched for ldap. ORA-12154: TNS:could not resolve the connect identifier specified Cause: A connection to a database or other service was requested using a connect identifier. . Check the type of naming adapters listed in the names.ora file.ora) Oracle Directory Naming Oracle Host Naming NIS Naming The net service name given in the connect string should be defined for at least one of the naming methods.ora fil e found will be used. Action: Check the alert_sid. do the following: 1. Cleari ng the Oracle Jar cache in the user profile directory of the client computer mak es sure that the fresh Forms Jar files are downloaded.ora file.ora file. For example. Its value is appended to the net service na me given in the connect string. 26) web address of database. The following example s hows the adapters: $ adapters . usin g the full name of the net service if necessary. The location is either the ORACLE_HOME/network/admin directory or the directory spec ified by the TNS_ADMIN environment variable. Either modify the codebase entry in your configuration file or replace the jar file in the codebase path with the appropriate jar file.ora file exists and is in the correct location. 4.ora file in the order given. The ldap.. This fully-qualified name should be the entry in the tnsnames. 2. if th e type of connect identifier used was a net service name then the net service na me could not be found in a naming method repository.ora file exists and is in the correct location. When using the directory naming method. 3.of the Jar file. This net service name should match the name in the tnsnames. or the net service name is a fully-qualified name. jdbc:oracle:thin:@hostname:1521:ORA11 27) issues with listener and tns ORA-03113: TNS:end-of-file on communication channel Cause: An error has occurred on the database server. and the connect identifier specified could not be resolved into a c onnect descriptor using one of the naming methods configured.

Remember that an IP address can be forged. 5. If the ldap. 3. – The ORACLE_HOME/ldap/admin directory. Verify that the directory has the default Oracle Context defined. then enable listener tracing to determine the client that made the request . and is defined in the local host n ame resolution service.168. you can configure parameters for access rights in the sqlnet.ora file does not exist. When using the external naming method. such as local hosts file. For example. Turn on tracing to determine which clients are timing out.– The directory specified by the TNS_ADMIN environment variable.2. or it may i ndicate that a malicious client is trying to cause a denial-of-service attack on the database server. Fatal NI connect error 12170. Use the ldapsearch utility or a directory administration tool to verify that the net service object exists in the Oracle Context at the location given by the value of the DEFAULT_ADMIN_CONTEXT parameter. 2. VERSION INFORMATION: TNS for Linux: Version 11.INBOUND_CONNECT_TIMEOUT.0. Restrict access to the client.ora file. as follo ws: – The DIRECTORY_SERVERS parameter defines the correct host and port for one or mor e valid LDAP servers.ora file.35)(PORT=52996)) If the time out occurs before the IP address can be retrieved by the database se rver.2. the following sqlnet. 2. DNS.ora to a largervalue. ORA-12170: TNS:Connect timeout occurred Cause: The client failed to establish a connection and complete authentication i n the time specified by the SQLNET. 2. Verify that the host name give is correct. then perform the following steps: 1.ora file are correct.2. then these parameters will be resolved usin g automatic discovery. – The ORACLE_HOME/network/admin directory.35. or SQLNE T.168. When using the Easy Connect naming method. 2. Verify that the LDAP server host and port are defined in DNS. Verify that the parameters defined in the ldap. – The directory specified by the LDAP_ADMIN environment variable. Reconfigure the SQLNET. Check that the net service name matches the tnsnames entry as described in th e preceding local naming section.0.0 Oracle Bequeath NT Protocol Adapter for Linux: Version 11.0 Time: 03-MAY-2009 13:51:12 Tracing to file: /ora/trace/svr_13279.SEND_TIMEOUT.RECV_TIMEOUT parameters in sqlnet. do the following: 1. – The DEFAULT_ADMIN_CONTEXT parameter defines the location of the Oracle Context i n this directory which should include the net service entry. then perform the following steps: 1. SQLNET.0.log excerpt shows a client IP address of 192. If you suspect a malicious client.trc Tns error struct: nr err code: 0 ns main err code: 12637 TNS-12637: Packet receive failed ns secondary err code: 12604 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.2. 4. This error may be a result of network or system delays. Verify that the NIS file for tnsnames is properly set up.log file on the database se rver to identify the source. Action: If the error occurred due to system or network delays that are normal fo r the particular environment.2. For example.INBOUND_CONNECT_TIMEOUT parameter in the sqln et. Locate the IP address of the client in the sqlnet.0.0 TCP/IP NT Protocol Adapter for Linux: Version 11.0. and so on. do the following: 1.0.

If USE_DEDICATED_SERVER is set to ON in the sqlnet. 3. dedi cated for dedicated server or shared for dispatchers. You can use the Listener Control utility SERVICES command to see what instances are currently registered . th en start it so that it can register with the listener. then ensure the database is configured to use dedicated servers.log file. Ensure that the service name specified in the connect descriptor is correct. then set this par ameter to OFF. You can use the Listener C ontrol utility SERVICES command to see what service handlers are currently regis tered with the listener. If the instance not running. but before the database instance has registered with the listener. 4. then pe rform the following steps: 1. The connect descriptor received by the listener specified a ser vice name for a service (usually a database service) that has either not yet dyn amically registered with the listener or has not been statically configured for the listener. TNS-12500/ORA-12500: TNS: listener failed to start a dedicated server process Cause: The listener failed to start the Oracle program. Ensure that the database instance is running. th en start it so that it can register with the listener. then ensure that the valu e is set to the appropriate service handler type for the database. Action: Perform the following steps: 1. or the database instance is not registered with the listener. If it is not. Action: Perform the following steps: 1. Check for an event in the listener. or the database instance is not registered with the listener. Possible reasons include : ■ The maximum number of processes allowed for a single user was exceeded ■ The listener does not have execute permission on the Oracle program ■ The associated Microsoft Windows service is not started In some cases. ORA-12520: TNS:listener could not find available handler for requested type of server Cause: The type of service handler requested by the client is incorrect or not r egistered for the requested SERVICE_NAME/INSTANCE_NAME. Action: If you suspect the problem is the wrong type of service handler. 2. Check which services are currently known by the listener by running the Liste ner Control utility STATUS or SERVICES command. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Cause: The listener received a request to establish a connection to a database o r other service. these errors can be caused by the same conditions which cause the following errors: ■ TNS-12549/ORA-12549 ■ TNS-00519 ■ TNS-12540/ORA-12540 ■ TNS-00510 ■ TNS-12560/ORA-12560 Action: Perform the appropriate action: ■ Increase the number of processes by setting the PROCESSES parameter in the datab ase initialization file to a larger value. and then try to connect a second time. 3. ■ Check the listener. that is. If (server=value) is set in the connect descriptor. Wait a moment. Ensure that the database instance is running. If the instance not running.log file for detailed error stack information. 2. This may be a temporary condition such as after the listener has s tarted.ora file. 2. Check that the SERVICE_NAME parameter in the connect descriptor specifies a s ervice name known by the listener. ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor Cause: The instance name in the connect descriptor is incorrect..

168. Locate the IP address of the client in the listener. For example.log file for detailed error stack information.35. Possible limits include: ■ The maximum number of processes allowed for a single user ■ The operating system is running low on paging space Action: Perform the appropriate action: ■ Increase the number of processes by setting the PROCESSES parameter in the datab ase initialization file to a larger value.log or listener. This error may be a result of network or system delays. Action: Perform the following actions: ■ Ensure that the supplied destination address matches one of the addresses used b y the listener.log file to identify the source. you can configure parameters for access rights in the sqlnet. then check the sqlnet. a TNS-12500/ORA-12500 error is also ret urned.2. the following listener. If the error persists.log file for detailed error stack informa tion. ■ Verify the client is pointing to the listener. these errors can be caused by the same conditions which ca use TNS-12549/ORA-12549 and TNS-00519 errors. Restrict access to the client. ■ Ensure the listener is listening on the host and port specified by the request.log excerpt shows a client IP address of 192.ora file. The third is an example of a limit wh ich can be increased by setting PROCESSES parameter in the database initializati on file to a larger value. or it may indicate that a malicious client is trying to cause a denial-of-service attack on the listener .log or listener. Possible limits include: ■ Number of open connections that Oracle Net can process simultaneously ■ Number of memory buffers which can be used simultaneously ■ Number of processes a particular database instance is allowed The first two are examples of hard limits. For example. ORA-12525: TNS:listener has not received client s request in time allowed Cause: The client failed to complete its connect request in the time specified b y the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener. TNS-12540/ORA-12540: TNS:internal limit restriction exceeded and TNS-00510: Internal limit restriction exceeded Cause: An internal limit has been exceeded. 03-MAY-2009 16:42:35 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=192. Action: Correct the protocol address. TNS-12541/ORA-12541: TNS:no listener Cause: The connection request could not be completed because the listener is not running.35)(PORT=53208)) * establish * <unknown sid> * 12525 TNS-12525: TNS:listener has not received client s request in time allowed TNS-12604: TNS: Application timeout occurred 2. Remember that an IP address can be forged. If you suspect a malicious client.168. then perform the following steps: 1.with the listener. ■ Check the sqlnet.2. ■ Verify that the listener is running at the address specified by the request. ORA-12533: TNS:illegal ADDRESS parameters Cause: The protocol specific parameters in the ADDRESS section of the designated connect descriptor are incorrect. TNS-12549/ORA-12549: TNS:operating system resource quota exceeded and TNS-00519: Operating system resource quota exceeded Cause: A quota or hard limit imposed by the operating system has been exceeded.ora file.ora to a larger value. such as an operating system error code to help identify which     . In some cases. Action: If the error occurred due to system or network delays that are normal fo r the particular environment. then reconfigure the INBOUND_CONNECT_TIMEOUT_liste ner_name parameter in listener. Action: Wait for the open connections to close and retry. In this case.

0006 00000003. Also suppose you have an index on the empno column.0000. TNS-12560/ORA-12560: TNS:protocol adapter error occurred Cause: There was an error when using a particular protocol. and 4 characters of file address. it must be understood that the data within the corrupt block is lost. You can find the name of the datafile with the corrup ted block by querying dba_data_files or v$datafile and using the file number fro m the ora-1578. If you do not run in archivelog mode. Enable OracleServicesid if it is disabled. these errors are caused by the same conditions which cause TNS-00510. Every row in a non-clustered table has a unique rowid pseudocolumn containing its address. If you run in archivelog mode. 5. This error may be du e to incorrect configuration of an ADDRESS parameter or may occur due to errors returned from the underlying protocol or operating system interface. ROWID FROM EMP WHERE EMPNO &gt.0001.1. so you can select from the table via the index and avoid the corrupt block by using the rowid in a where clause. 4. and rename the datafile to the new locati on before you recover. 4 characters of row address. Enter MSCONFIG in the Open field. the first thing to do is to find out what object is corrupted. If the corruption is the result of a bad disk. If the segment is an index. startup mount. Select Run from the Microsoft Windows Start menu. In some cases. Check that Oracle Services has started. Suppose you have corrupted table emp with columns empno.quota has been exceeded. a period. 3. Perform the following actions: 1. If we issued SELECT EMPNO. TNS-00519. Restart the computer. ename and deptno. 28) corrupt blocks in the table space 1. 2. You will want to correct your hardware problem before you restor e. The following query will tell you: SELECT SEGMENT_NAME. you can restore the datafile from backup to a good disk. simply drop and recreate it. Indexes hold rowids for each row in a table. a period. ROWID: The rowid is in hexidecimal and is 18 characters long: 8 characters of block address. 0. 6. TNS-12549/ORA-12549 errors.0006 . SEGMENT_TYPE FROM DBA_EXTENTS WHERE FILE_ID = f AND b BETWEEN BLOCK_ID AND BLOCK_ID + BLOCKS . we would get something like: empno ----100 101 rowid ----00000003. If the segment is a table. TNS-12540/ORA-12540. Go to the Services tab. the best resolution is to restore the fil e from backup and recover. Action: This error occurs on Microsoft Windows systems only.

0006 00000004. ROWID FROM EMP WHERE EMPNO &gt.0000.000A You could create a new table with the same definition as the emp table: CREATE TABLE TEMP AS SELECT * FROM EMP WHERE 1 = 2. 0 EMPNO ----500 501 ROWID ----00000004. . 755 756 00000003. . . 500.0001. 501. 500 501 .0003. 00000.000A 0000001A. .000A . You then need to find out from     AND ROWID LIKE    00000004. block # 4) You can find all of the empnos for employees in the corrupted blocks with: SELECT EMPNO. Assume that you had: 01578. and then insert into that table around the corruption: INSERT INTO TEMP SELECT * FROM EMP WHERE EMPNO &lt.0006 00000003.000A Note that if the index were on a character column we would change the above query to WHERE EMPNO &gt. Then drop the original table and rename temp. .0001.%.000A 0000001A.0000.000A 00000004. .000A 00000004.000C.0002. "ORACLE data block corrupted (file # 10.0005.102 103 . INSERT INTO TEMP SELECT * FROM EMP WHERE EMPNO &gt.

EMP.backups or paper records what information you have lost for empnos 500 and 501. You would then issue: CREATE TABLE TEMP AS SELECT * FROM EMP WHERE 1 = 2. database trigger ?     AND ROWID NOT LIKE 00000004. 0 This gives you all empnos which were not in the corrupt block. EMPNOS WHERE EMP.EMPNO &gt. 29) 30) 31) 32) recovery of diff types of tablespace. If you had many different rows in the corrupt block it might be easier to issue the following: CREATE TABLE EMPNOS AS SELECT EMPNO FROM EMP WHERE EMPNO &gt.DEPTNO FROM EMP.000A .%. INSERT INTO TEMP SELECT EMP. . how do you check performance issues in your database. 8. 0 AND EMP. EMP.ENAME.EMPNO.EMPNO = EMPNOS.EMPNO. ticketing flow.

Sign up to vote on this title
UsefulNot useful