Skip to main content

Information Technology Gear

Search This Blog

Computer Quizes

on March 10, 2016

Get link
Facebook
X
Pinterest
Email
Other Apps

Practice Quiz 1

Practice Quiz 2

Practice Quiz 3

Practice Quiz 4

Practice Quiz 5

Practice Quiz 6

Practice Quiz 7

Quiz for Competitve Exams

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Change Location of Alert Log/Trace File Oracle 11g

SQL> show parameter diag Above command will show the Alert file and trace location. NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ diagnostic_dest string /oracle/app/oracle SQL> Alter System Set Diagnostic_Dest=' /oracle/app/oracle/tracedest'; It will change the Trace Files location. SQL> show parameter diag NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ diagnostic_dest string /oracle/app/oracle/tr...

RMAN-06820: WARNING: failed to archive current log at primary database

RMAN-06820: WARNING: failed to archive current log at primary database ORACLE error from target database: ORA-17629: Cannot connect to the remote database server ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor ORA-17629: Cannot connect to the remote database server Description - In a data guard environment backup of archivelog files takes backup of the current standby redo logfile also, that result a required online redo log switch on the primary database before backup of the current standby redo logfile. because of this change, passwordfile authentication is required to have a successful redo log switch at the primary database. In Oracle 11.2.0.4, use rman target sys@<your tnsnames> instead of rman target / e.g. rman target sys@'(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION=(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PRO...

Prerequisite of OEM Agent Installation on Windows Server Failed Due To Fully Qualified Domain Name

Scenario - ORACLE Database was already running and hostname was TESTDB. While installation of OEM 13c Agent, below error was coming during prerequisite check. Performing check for CheckHostName Is the host name valid? value of oracle_hostname:192.168.0.1 value of hostname is: TESTDB Expected result: Fully qualified domain name, for example foo.mydomain.com Actual Result: 192.168.0.1. Ensure that you provide a fully qualified domain name. Check complete. The overall result of this check is: Failed <<<< Check complete: Failed <<<< Problem: The host name specified for the installation or retrieved from the system is incorrect. Recommendation: Ensure that your host name meets the following conditions: (1) Does NOT contain localhost.localdomain. (2) Does NOT contain any IP address. (3) Ensure that the /etc/hosts file has the host details in the following format. ...

Powered by Blogger