Database Reference
In-Depth Information
11 '/media/backup/NCDB/NCDB/sysaux01.dbf' ,
12 '/media/backup/NCDB/NCDB/undotbs01.dbf' ,
13 '/media/backup/NCDB/NCDB/users01.dbf'
14 CHARACTER SET WE8ISO8869P15;
Control file created.
Notice how the create controlfile statement references the image copies made available to the development
server via NFS. Following this step you need to execute the rename.sql script. It will rename the files pointing them to
the NFS mount. The directory /m/CLONE—exported from the NFS appliance—is mounted to /u01/oradata/CLONE
on the development server.
begin
DBMS_DNFS.CLONEDB_RENAMEFILE(
'/media/backup/NCDB/system01.dbf', '/u01/oradata/CLONE/system01.dbf');
DBMS_DNFS.CLONEDB_RENAMEFILE(
'/media/backup/NCDB/sysaux01.dbf', '/u01/oradata/CLONE/sysaux01.dbf');
DBMS_DNFS.CLONEDB_RENAMEFILE(
'/media/backup/NCDB/undotbs01.dbf', '/u01/oradata/CLONE/undotbs01.dbf');
DBMS_DNFS.CLONEDB_RENAMEFILE(
'/media/backup/NCDB/users01.dbf', '/u01/oradata/CLONE/users01.dbf');
end;
/
This step will only succeed if the destination location is an NFS mount. Although it is theoretically not needed to
recreate the create controlfile script every time, you should still develop a habit to do so. If someone added a data file
to the production system in the meantime this data file will not be in the controlfile and you have to start over. After
completion of this step you can open the database with the resetlogs option. Don't forget to add temp-files and other
auxiliary structures you may need! If you verify the database files now using the “sparse” flag, you will see that they
really take little or no space on disk:
[oracle@server2 ~]$ ls -lsh /u01/oradata/CLONE/*.dbf
total 220K
92K -rw-r-----. 1 oracle oinstall 551M Nov 13 22:45 sysaux01.dbf
16K -rw-r-----. 1 oracle oinstall 211M Nov 13 22:45 system01.dbf
16K -rw-r-----. 1 oracle oinstall 1.6G Nov 13 22:45 undotbs01.dbf
16K -rw-r-----. 1 oracle oinstall 5.1M Nov 13 22:45 users01.dbf
The first column indicates the actual space used, and the familiar figures in the middle of the output show the
size the file would occupy if this was a full-sized copy. The space savings are immediately visible.
Deprecation of OEM DB Console
Oracle has removed the Database Console which it introduced with Oracle 10g with immediate effect. There is
no further warning: it is gone with Oracle 12c. Although unexpected, this step should not cause trouble to most
organizations that rely on centralized monitoring solutions such as OEM 12c Cloud Control. The replacement
however is very neat and deserves a closer look, even though it requires Flash for it to operate.
During the database creation the Database Creation Assistant will assign an unused port for DB Express, on most
systems this will be 5500. The documentation states that this port is also the HTTPS Port for XML DB, which is no
longer an optional component of the database.
 
Search WWH ::




Custom Search