Just a simple recording of the “startup” & “shutdown” process in Oracle 220.127.116.11 both form the front-end commands and the back-end recorded logging with alert log file, may some details be discovered in this close look and more understandings to what Oracle’s doing in each of the step.
About the “startup”
[oracle@stonedb ~]$ alias | grep conn alias connme='sqlplus / as sysdba' [oracle@stonedb ~]$ connme SQL*Plus: Release 18.104.22.168.0 Production on Sat Dec 1 10:03:56 2012 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to an idle instance. SQL> startup ORACLE instance started. Total System Global Area 368263168 bytes Fixed Size 1345016 bytes Variable Size 276826632 bytes Database Buffers 83886080 bytes Redo Buffers 6205440 bytes Database mounted. Database opened.
It was great that the database do not have to be shutdown and then be mounted to just enable the flashback on feature in Oracle 11G, at least 11.2 later.
Below is a short testing case to utilize this feature to prepare some Application release just in case a rollback is requested, and the flashback could be faster than the Rman backup & restore.
Check and Change the DB working mode:
oracle@dbinterest ORADB112:/oracledb/ora> sqlplsu / as sysdba SQL*Plus: Release 22.214.171.124.0 Production on Fri Nov 23 03:47:59 2012 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production With the Partitioning, Oracle Label Security, OLAP, Data Mining, Oracle Database Vault and Real Application Testing options SQL> select log_mode,flashback_on from v$database; LOG_MODE FLASHBACK_ON ------------ ------------------ NOARCHIVELOG NO
Put the DB at the mounted state, then change the log mode.
Read the rest of this entry »
Oracle 11203 Rman backup check around for exploring purpose:
[oracle@stonedb ~]$ [oracle@stonedb ~]$ rman target / Recovery Manager: Release 188.8.131.52.0 - Production on Tue Nov 6 23:15:01 2012 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: STONE11G (DBID=1598568833) RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name STONE11G are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/database/11.2.0/dbs/snapcf_STONE11G.f'; # default RMAN>
While using “awrextr.sql” to export historical AWR data for the purpose of planning, analyzing and troubleshooting, the Oracle error message “ORA-06502: PL/SQL: numeric or value error: character string buffer too small” blocked on the way.
Part of the error mesg:
Using the dump directory: DIR_NAME01 Specify the Name of the Extract Dump File ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The prefix for the default dump file name is awrdat_100231_103139. To use this name, press <return> to continue, otherwise enter an alternative. Enter value for file_name: ABCDEFG_AWREXTRACT_100231_103139 Using the dump file prefix: ABCDEFG_AWREXTRACT_100231_103139 begin * ERROR at line 1: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at line 2 Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
Just a simple note taking of Larry’s opening keynote, hopefully to find some sparkling ideas behind the talk.
Here’s the mindmap (This may takes you a bit of time to load, and might need your java be updated) of the keynote and below are the PPT screenshots from Larry’s keynote.
The Youtube channel (The video could be found here)
Oracle has a nice explanation on what ADRCI(ADR Command Interpreter) and ADR(Automatic Diagnostic Repository) are …
is a command-line utility that enables you to investigate problems, view health check reports, and package and upload first-failure diagnostic data to Oracle Support. You can also use the utility to view the names of the trace files in the Automatic Diagnostic Repository (ADR) (ADR) and to view the alert log. ADRCI has a rich command set that you can use interactively or in scripts.
is a file-based repository that stores database diagnostic data such as trace files, the alert log, and Health Monitor reports. Key characteristics of ADR include:
- Unified directory structure
- Consistent diagnostic data formats
- Unified tool set
The preceding characteristics enable customers and Oracle Support to correlate and analyze diagnostic data across multiple Oracle instances, components, and products.
ADR is located outside the database, which enables Oracle Database to access and manage ADR when the physical database is unavailable. An instance can create ADR before a database has been created.
Following are some of the news around the Oracle [12c] from different news Channel, here just picks up some of the brief ideas and makes a records:
- Oracle gears up for infrastructure cloud and 12c database launches (www.channelregister.co.uk)
- Oracle Details 12C Database, Exadata X3, New Cloud Services (www.eweek.com)
- Larry Ellison: Oracle Has Invented A New Kind Of Database (www.businessinsider.com)
- Oracle sheds more light on database 12c, Exadata X3 (www.computerworld.com)
- Oracle CEO Ellison reveals more details about ‘multitenant’ 12c database (www.computerworld.com)
- How Oracle’s pluggable databases will work (www.computerworld.com)
Pluggable databases will allow multiple databases to run under one copy, or instance, of the Oracle database software, a feature he called “multitenancy.”
In a nutshell, the new design splits today’s database into two separate entities, an act Llewellyn called “architectural separation.” One portion, often referred to as the Root or the container database, will hold all the functionality and metadata required to run the database itself. The second portion will be the user’s database and it will be independent from the container database.
The pluggable database is inherently more efficient for a number of reasons, Rajamani later explained. Today, a server running 100 databases must switch rapidly between all those databases, which creates a lot of overhead. “A hundred binaries are going to 100 context switches,” he said. A single database eliminates all this task switching. Also, each database has a large number of background processes that need to run continuously, and reducing all of these processes to a single set saves resources.
Also, having a single copy of database software to handle multiple user databases reduces the amount of disk space needed, since it eliminates the multiple copies of the host database software. (Oracle did not disclose how this new architecture would affect licensing costs.)
Gupta did note that the new architecture would also raise a number of challenges. Organizations may have to rethink how to allocate computational resources, he said. Database administrators will have to determine the new workload characteristics of running multiple databases on a single server. The optimum size of a server, in reference to memory and storage space, may also need to be reconsidered.
“Databases coming from separate servers to one server will pose some challenges in performance management,” Gupta said.
There’re 2 interfaces for checking Oracle ASM related information. One is the asmcmd. And the other the unified sql*plus interface.
The sql*plus interface is a familiar to DBAs, and Oracle makes the ASM management via this unified and powerful tool will likely not add too much stress on the DBAs, but will show up a new idea of managing storage related files from the sql*plus tool.
From the look, the ASMCMD commands are more or less similar to the Linux/Unix commands. So it should not be a problem if you have been daily in the nix environment. Just give it a check around to see any differences and get familiar with them. This reminds me also of the hadoop hdfs commands, which are also quite similar to the nix ones. Developers for those products don’t want put too much learning curves on whatever new stuff coming out and want to make it as simple as possible. And in that way, more people will like to give it a try. Make things easier is not an easy thing
Just record some testing and exploring around the old version of Oracle RAC 10.2.0.1 even the Oracle database 12c is just around the corner. Kind of feeling how fast the technology is moving forward…
After shutdown all the elements and bounce the RAC server, by default, Oracle CRS, ASM, DB will automatically start. Below is the check on the status of different parts just after a fresh start, no any other activities going:
- All processes related to “oracle”:
It could be a pain to configure the Passwordless SSH on multinodes, say hundreds or thousands of nodes a cluster. So it would be great to automate this process, especially in the beginning of setup a testing environment.
The linux utility/tool/program “expect” is a good candidate in serving this purpose. After fighting many of the different error mesgs in the process of composing the automation script, finally a working version works well on my 3 testing nodes to allow the specific user to access each of the nodes in the cluster without prompt for password.
There’re mainly 2 scripts, including “sshpass.sh” and “ssh4slaves.sh”, where the 1st script will call the 2nd one in the process to config all the nodes in the cluster.