Install Oracle in silent mode 12C Release 1 (12.1)

This article presents how to install Oracle 12C Release 1 in silent mode.

Silent mode installation allows to configure necessary Oracle components without using graphical interface nor any interaction with end user. It’s very useful method especially when you want to prepare standard installation using shell scripts.

Read following article to install OEL6 Linux: Install Oracle Linux 6 64 bit(for comfort set 4G memory for your virtual machine). During OEL6 installation I drop user oracle and both group dba and oinstall.

Software

Software for 12CR1 is available on OTN or edelivery

Database software

linuxamd64_12102_database_1of2.zip 
linuxamd64_12102_database_2of2.zip

Requirements

Be sure you fulfil following:

  • Oracle Linux 6 with the Unbreakable Enterprise kernel: 2.6.39-200.24.1.el6uek.x86_64 or later
  • Oracle Linux 6 with the Red Hat Compatible kernel: 2.6.32-71.el6.x86_64 or later

Continue reading

Install Oracle in silent mode 11G Release 2 (11.2)

This article presents how to install Oracle 11G Release 2 in silent mode.

Silent mode installation allows to configure necessary Oracle components without using graphical interface nor any interaction with end user. It’s very useful method especially when you want to prepare standard installation using shell scripts.

Read following article how to install Oracle Enterprise Linux 6: Install Oracle Enterprise Linux 6 (for comfort set 4G memory for your virtual machine before proceeding with Oracle software installation).

Installation software is available on OTN version 11.2.0.1 or metalink 11.2.0.4. In this installation I’m presenting installation for 11.2.0.4 but for previous version 11.2.0.X it shouldn’t be different.

Following components will be installed in silent mode:

  • oracle binaries: Oracle Enterprise Edition 11G Release 2
  • network components: listener LISTENER
  • database components: database ORA11G.dbaora.com and database console

Oracle software that was verified

release 11.2.0.4

p13390677_112040_Linux-x86-64_1of7.zip 
p13390677_112040_Linux-x86-64_2of7.zip

Continue reading

Define SecureFile LOBs during import Oracle Database 12C release 1 (12.1)

In Oracle 12C it’s possible to define LOB storage method during import time independent from export settings.

It gives more flexibility during importing data.

impdp .. TRANSFORM=LOB_STORAGE:SECUREFILE|BASICFILE|DEFAULT|NO_CHANGE
  • DEFAULT – no lob storage clause is set for CREATE TABLE
  • NO_CHANGE – use settings from dump file
  • BASICFILE – creates LOBs as basicfile
  • SECUREFILE – creates LOBs as securefile
  • Can be set in PL/SQL using DBMS_DATAPUMP.METADATA_TRANSFORM

Example

Imports data and sets LOBs as SECUREFILE

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp
TRANSFORM=LOB_STORAGE:SECUREFILE

Have a fun :)

Tomasz

Compress tables during import Oracle Database 12C release 1 (12.1)

In Oracle 12C it’s possible to specify during import compressions settings for a table independent from export settings.

It gives more flexibility during importing data.

impdp .. 
TRANSFORM=TABLE_COMPRESSION_CLAUSE:NONE|"<compression type>"
  • NONE – compression ignored during import, taken from tablespace settings
  • <compression type> – valid compression clause:
    • NOCOMPRESS : Disables table compression.
    • COMPRESS : Enables basic table compression.
    • ROW STORE COMPRESS: Same as COMPRESS.
    • ROW STORE COMPRESS BASIC : Same as COMPRESS.
    • ROW STORE COMPRESS ADVANCED : Enables advanced compression, also known as OLTP compression.
    • COLUMN STORE COMPRESS FOR {QUERY|ARCHIVE} : Hybrid Columnar Compression (HCC) available in Exadata and ZFS storage appliances.
  • Can be set in PL/SQL using DBMS_DATAPUMP.METADATA_TRANSFORM

Example

Import data with dedicated compression type

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp
TRANSFORM=TABLE_COMPRESSION_CLAUSE:"ROW STORE COMPRESS"

Have a fun :)
Tomasz

ENCRYPTION_PWD_PROMPT=Y Oracle Database 12C release 1 (12.1)

There is new option to pass in silent mode encryption password in Oracle 12C during exporting sensitive data. In new version user is asked about password during execution of export.

expdp ... ENCRYPTION_PWD_PROMPT=Y ...
...
Password: <user is asked for encryption password>

In previous version encryption password was explicit passed to expdp using parameter ENCRYPTION_PASSWORD. So could be visible via ps command or in a expdp parameter script.

Features:

  • new parameter ENCRPTION_PWD_PROMPT as default set to N
  • if the parameter is set to Y then user is asked for encryption password during export
  • the password is not visible via commands like PS nor stored in scripts
  • old 11g ENCRYPTION_PASSWORD and ENCRYPTION_PWD_PROMPT=Y can’t be used in the same time and generate an error

Have a fun :)
Tomasz

Exporting views as tables Oracle Database 12C release 1 (12.1)

This feature extends functionality of Data Pump 12C. It allows to export views as tables.

expdp .. VIEWS_AS_TABLES=[schema_name.]view_name ...

Features

  • new parameter for expdp VIEWS_AS_TABLES
  • it exports view as table definition plus data
  • it exports dependent objects like constraints(on the view) and grants(on the view)
  • very useful to export subset of a data from table(s) via complex view
  • during import as first step table is created then data is imported
  • it can be exported in PL/SQL using DBMS_DATAPUMP.METADATA_FILTER
  • doesn’t support views that reference object type or functions
  • unloads data as unencrypted format

Examples

Export of view emp_view”as table and table departments

expdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp
VIEWS_AS_TABLES=emp_view TABLES=departments

Export of two views as tables emp_view and oe.orders_v

expdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp
VIEWS_AS_TABLES=emp_view,oe.orders_v

Import of exported view as table emp_view and rename the table as emp_new_table

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp
VIEWS_AS_TABLES=emp_view REMAP_TABLE=emp_view:emp_new_table

Import through data base link db_link via view emp_v and loading it directly to existing table employees

impdp hr/hr VIEW_AS_TABLE=emp_v NETWORK_LINK=db_link
REMAP_TABLE=emp_v:employees TABLE_EXIST_ACTION=append

Have a fun :)

Tomasz

 

 

Disabling LOGGING for import Oracle Database 12C release 1 (12.1)

It’s very nice feature available in Data Pump 12C. It allows to disable generation of redo logs during import of  a data into database.

impdp .. TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y|N[:TABLE|INDEX]

Features

  • DISABLE_ARCHIVE_LOGGING as default is set to N
  • it’s possible to set it only for TABLES or INDEXES or for both
  • if used then once import is finished original logging settings for imported objects are restored
  • redo data is not written into disk
  • faster load data into database less I/O operations
  • great for large data loads or populating new databases
  • It’s recommended to make a full database backup  after such load
  • small amount of log activity is still still generated by the import
  • FORCE LOGGING set on database level will ignore the settings
  • operations against master data pump table(the table stores activity of data pump jobs)  are always using logging option

Examples

Disable logging for whole imported file so for tables and indexes

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp SCHEMAS=hr 
TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y

Disable logging just for indexes

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp SCHEMAS=hr 
TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y:INDEX

Disable logging just for indexes – different way

impdp hr/hr DIRECTORY=dpdump_dir DUMPFILE=hr.dmp SCHEMAS=hr 
TRANSFORM=DISABLE_ARCHIVE_LOGGING:Y
TRANSFORM=DISABLE_ARCHIVE_LOGGING:N:TABLE

Have a fun :)
Tomasz