Wednesday, August 22, 2012

How to Create Full SQL Database backup commands

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Execute the BACKUP DATABASE statement to create the full database backup, specifying:

* The name of the database to back up.
* The backup device where the full database backup is written.

The basic Transact-SQL syntax for a full database backup is:

BACKUP DATABASE database
TO backup_device [ ,...n ]
[ WITH with_options [ ,...o ] ] ;
Option Description
database
Is the database that is to be backed up.
backup_device [ ,...n ]

Specifies a list of from 1 to 64 backup devices to use for the backup operation. You can specify a
physical backup device, or you can specify a corresponding logical backup device, if already
defined. To specify a physical backup device, use the DISK or TAPE option:

{ DISK | TAPE } =physical_backup_device_name
For more information, see Backup Devices.
WITH with_options [ ,...o ]

Optionally, specifies one or more additional options, o. For information about some of the basic
with options, see step 2.

2.

Optionally, specify one or more WITH options. A few basic WITH options are described here. For
information about all the WITH options, see BACKUP (Transact-SQL).
* Basic backup set WITH options:

{ COMPRESSION | NO_COMPRESSION }

In SQL Server 2008 Enterprise and later only, specifies whether backup compression is performed
on this backup, overriding the server-level default.
Get Oracle Certifications for all Exams
Free Online Exams.com

Reports Cache Directory in Oracle E-Business R12 is Growing Rapidly

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

The cache files are not being deleted when the cacheSize property is exceeded and files are also not deleted even after enabling and setting maxCacheFileNumber, which is the documented method.

Solution

Workaround:

  1- Shutdown the Concurrent Processing server.
  2- Manually delete all the temporary files under the $INST_TOP/logs/ora/10.1.2/reports/cache path
  3- Startup up the Concurrent Processing server.

OR

Change the Oracle Reports configuration file $INST_TOP/ora/10.1.2/reports/conf/rwbuilder.conf and bouncing the services. 

CHANGE: 
<property name="cacheSize" value="50"/> to 
<property name="cacheSize" value="0"/> 

NOTE: This change will be lost when Autoconfig is run. Apply patch 8602992 as soon as it becomes available.

Permanent Fix:

  1- Apply the following Patch 8602992.

Important Note: If facing Intermittent Oracle Reports REP-0069: REP-57054 Errors after applying the patch above please review Note 1237834.1 - Intermittent Oracle Reports REP-0069: REP-57054: Error

Get Oracle Certifications for all Exams
Free Online Exams.com

EBS R12 Oracle Reports Cache Directory Not Being Cleaned Up

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Applies to:

Oracle Applications Technology Stack - Version 12.0 to 12.0 [Release 12.0]
Information in this document applies to any platform.
Oracle Reports, Cache, Cleaned Up, $INST_TOP, purge, disk space, temporary, files


Symptoms

In E-Business Suite (EBS) Release 12, when concurrent requests of the 
execution method of Oracle Reports are submitted, temporary files are present 
under the path of $INST_TOP/logs/ora/10.1.2/reports/cache. 

The temporary files are identical to the file placed under the 
$APPLCSF/$APPLOUT path, however. These temporary files are not purged when 
the "Purge Concurrent Request and/or Manager Data" (FNDCPPUR) program runs. 

Cause

New Bug 8449763 / 8602992 due to the new architecture of EBS R12

Solution


1. Perform both of the following actions:

a) Apply patch 8602992 "APPS1012: CACHE DIRECTORY NOT BEING CLEANED OUT"--currently available via MOS (Metalink). 

b) Apply technology stack template fix patch 9032800 "SET CACHESIZE=0 RWBUILDER_CONF_1012.TMP"--as soon as it becomes available.

As a current workaround to patch 9032800:

Change the Oracle Reports configuration file $INST_TOP/ora/10.1.2/reports/conf/rwbuilder.conf and bouncing the services. 

CHANGE: 
<property name="cacheSize" value="50"/> to 
<property name="cacheSize" value="0"/> 

NOTE: This change will be lost when Autoconfig is run. Apply patch 8602992 as soon as it becomes available. 

NOTE 2:   Patch 8602992 will ensure that the Oracle Report rwrun executable deletes the cache file after the report runs, however. Any existing cache file prior to the fix will need to be deleted manually

Get Oracle Certifications for all Exams
Free Online Exams.com