Products of the year

“It is worth noting that in the past Sun has been able to dominate many categories, but it took multiple products to achieve that distinction. This year one product, NetBeans, dominated the categories by winning five out of twelve.” – Developer.com

Congratulations to NetBeans! They won following categories.

* Development Tool – NetBeans Platform
* Development Utilities – NetBeans Profiler
* Wireless/Mobile – NetBeans Mobility Pack for Connected Device Configuration (CDC) 5.5
* Java Tool – NetBeans IDE
* Open Source – NetBeans

I’m using NetBeans and find that it is a good IDE for Java development although I prefer JDeveloper. However the developers voted therefore it’s their choice. Here is the link to the post:

* Winners of the Developer.com Product of the Year 2009 Are Announced

How to change the IAS_Admin password (Oracle 9i)

If you want to change the IAS_Admin password, you need to delete the <credentials> line associated with ias_admin in the jazn_data.xml file. However, you would need to shut down the EMWebsite prior to doing this.

.Edit the following file and locate the line that defines the credentials property for use the ias_admin user:

%ORACLE_HOME%\sysman\j2ee\config\jazn-data.xml

The following example shows the section of jazn-data.xml with the credentials entry in boldface type:

<realm>
<name>enterprise-manager</name>
<users>
<user>
<name>ias_admin</name>
<credentials>rJqp85BkhFwAyw9ddl0PnFlUBVaWzbfT</credentials>
</user>

2.Remove the entire line that contains the <credentials> property from jazn-data.xml.

3.Enter the following command from DOS Command window:

%ORACLE_HOME%\bin\emctl set password reset <new password>

The steps outlined in the previous lines work, BUT you have to reboot the machine in order for you to pick up the new password. You can’t simply stop/restart the server, because when you try that, it will ask you for the ias_admin password. But a shutdown/restart will work. Been there and survived!

Actually, you can do an emctl restart since emctl stop asks for the password, but start and restart do not

Be happy administrator

^ ^
Minh Tran

ORA-39700 in alert log when recover from a full backup

ORA-39700:	database must be opened with UPGRADE option
Cause:	A normal database open was attempted, but the database has not been upgraded to the current server version.
Action:	Use the UPGRADE option when opening the database to run catupgrd.sql (for database upgrade), or to run catalog.sql and catproc.sql (after initial database creation).

Complete the following sections to upgrade an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.4: 1. {Run the Pre-Upgrade Information Tool} 2. {Upgrading a Release 10.2 Database} 3. {Missing Components When Upgrading} 9.3.2.1 Run the Pre-Upgrade Information Tool If you are upgrading database manually, then you should analyze it by running the Pre-Upgrade Information Tool. The Pre-Upgrade Information Tool is a SQL script that ships with Oracle Database 10.2. Complete the following procedure to run the Pre-Upgrade Information Tool: 1. Start the database in the UPGRADE mode: SQL> STARTUP UPGRADE 2. Set the system to spool results to a log file for later analysis: SQL> SPOOL upgrade_info.log 3. Run the Pre-Upgrade Information Tool: SQL> @?/rdbms/admin/utlu102i.sql 4. Turn off the spooling of script results to the log file: SQL> SPOOL OFF Check the output of the Pre-Upgrade Information Tool in the upgrade_info.log file. The following is an example of the output generated by the Pre-Upgrade Information Tool: here exemple output and then After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home: Note: If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log. 1. Log in with administrator privileges. 2. For Oracle RAC installations, start listener on each node of the cluster as follows: C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start listener -n node 3. If you are using Automatic Storage Management, start the Automatic Storage Management instance. 4. For single-instance installations, start the listener as follows: C:\> lsnrctl start 5. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: C:\> sqlplus /NOLOG SQL> CONNECT SYS AS SYSDBA Enter password:SYS_password Users of single-instance installations now proceed to step 7. 6. For Oracle RAC installations: 1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: C:\> sqlplus /NOLOG SQL> CONNECT SYS AS SYSDBA Enter password: SYS_password SQL> STARTUP NOMOUNT 2. Set the CLUSTER_DATABASE initialization parameter to FALSE: SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; 3. Shut down the database: SQL> SHUTDOWN 7. Enter the following SQL*Plus commands: SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catupgrd.sql SQL> SPOOL OFF 8. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script. This list provides the version and status of each SERVER component in the database. 9. If necessary, rerun the catupgrd.sql script after correcting any problems. 10. Restart the database: SQL> SHUTDOWN IMMEDIATE SQL> STARTUP 11. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended. SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql Note: When the 10.2.0.4 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 54 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.

Multiple ORACLE_HOME on same machine

We can install different oracle versions on same machine like Oracle 8i,9i or 10g. Also, we can create multiple database/instance on a single machine but remember to name them differently, for  example: db1,db2,db3 and so on. When name them like that, we avoid conflicting installing them on our single machine.

Suppose we planned to install oracle 8i,9i or 10g on same machine then we need to set oracle enviourment variable to point LATEST VERSION. Like this one:

ORACLE_SID=SIDNAME
ORACLE_HOME=10ORACLECHOME
PATH=$ORACHOME/bin(10G)
TNS_ADMIN=$ORACLE_HOME/network/admin(10g)
After that, we can configure LISTENER.ORA we use for three different version. There is two option for this.
First one: create separate listener.ora file for each version like

1. listener with default port(1521)
2. listener1 with separate port
3. listener2 with separate port

   or

Second one: use only one listener.ora file for all three oracle homes. To do so, please follow following instructions:
1. Stop listener services of Oracle 8i,9i database
2. create listener.ora file for 10g. and edit 10g listener.ora file then do configure for oracle 8i or 9i database like below:

LISTENER=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=sale-server)(PORT=1521))
(ADDRESS=(PROTOCOL=ipc)(KEY=extproc))))

SID_LIST_LISTENER=
(SID_LIST=

(SID_DESC=
(GLOBAL_DBNAME=Ora8i)
(ORACLE_HOME=/oracle8i)
(SID_NAME=Ora8i))

(SID_DESC=
(GLOBAL_DBNAME=Ora9i)
(ORACLE_HOME=/oracle9i)
(SID_NAME=Ora9i))

(SID_DESC=
(GLOBAL_DBNAME=Ora10g)
(ORACLE_HOME=/oracle10g)
(SID_NAME=Ora10g))

(SID_DESC=
(SID_NAME=plsextproc)
(ORACLE_HOME=/oracle10g)
(PROGRAM=extproc)))

So please enjoy,

Minh Tran

RemoteOperationException – Wrong Password for User

RemoteOperationException:

ERROR:Wrong Password for User. I was able to resolve this issue by adjusting security policies in the OS. My assumption was that the administrator would have the necessary policies, however that was not the case. To resolve this issue, follow the steps below:
1. Control Panel, Administrative Tools.
2. Click on Local Security Policy.
3. Local Policies, User Rights Assignment.
4. Double click, ‘Log on as a batch job’.
5. Add your local user that you are supplying for the Host Credentials (Administrator in my case).

Log out of Windows, then log back in. Hit the EM web site, log in and attempt to schedule, import/export, etc.

Hopefully this will resolve your problem.