java.lang.ClassNotFoundException: oracle.forms.engine.Main

Oracle Application Server 10g has a form service to run a form on the web,
Start -> Programs ->Oracle Application Server 10g -> Forms Services -> Run a form on the web for form=test.fmx

If the applet is not display correctly and receive the error:
java.lang.ClassNotFoundException: oracle.forms.engine.Main

you should check if JInitiator already installed.

If already installed, then check in
Control Panel -> JInitiator administration console , the option “Use browser settings” and “use proxies” has to be unchecked.

Add Y!M and Live M Online Status to Web Pages

Add Yahoo! Messenger and Windows Live Messenger Online Status to Web Pages

Online status icon allows people who visit your web page to see if the you currently online using Yahoo! Messenger or Windows Live Messenger.

There are many places where you can insert your online presence. Some examples include:
- Your Homepage
- Your Weblog
- Your Online Journal
- Message Boards

You can get online status for Yahoo! Messenger at Add Presence, just type your Yahoo! ID then copy and paste the HTML text below it into your web document.

If a visitor of your web page clicks your online status, an instant message window will open for them so they can type you an instant message to contact online with you.

And to get HTML code for Live Messenger online status, you can get at page Live Messenger Settings. But first you must be login and then check list the option “Allow websites to see your Messenger status and send you messages”. Then you click link of “Create HTML” and choose the appropriate control you desire. Final step, copy the HTML and paste it into your webpage.

There is another service that provide service that lets you put a small image on a web page to show if you are online on AOL Instant Messenger, ICQ, IRC, Jabber, MSN Messenger, Skype, and Yahoo Messenger.

^_^

Create or Export data from MDB to DBF

To export data that have been query by “SELECT … FROM” in mdb file to dbf file, you can use this sample query :

SELECT * INTO [dBase IV;database=C:\].newdbf FROM bank

ORA-00257: archiver error. Connect internal only, until freed.

ORA-00257: archiver error. Connect internal only, until freed.
Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.

Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

———————————-

I clear some archivelog that have fill up until server harddisk has no space anymore. After clear some archivelog, then automatically the message not display anymore.

ORA-09275: CONNECT INTERNAL

ORA-09275: CONNECT INTERNAL is not a valid DBA connection
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
Action: Please try to connect AS SYSDBA or AS SYSOPER.

INTERNAL is a desupported account,

use :

- CONNECT SYS/PASSWORD AS SYSDBA

or

- CONNECT / AS SYSDBA

instead.

Connect Remotely as SYSDBA using orapwd

- Set init parameter to REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE.

parameter be set to either SHARED or EXCLUSIVE.
SHARED the password file can be used by multiple databases and only the SYS user is recognized.
EXCLUSIVE the password file can be used by only one database and multiple users can exist in the file.

The parameter value can be confirmed by:

SQL> show parameter password

NAME TYPE VALUE

—————————– ———– ———-
remote_login_passwordfile string EXCLUSIVE

- Create the password file using the ORAPWD utility.

orapwd file=<filename> password=<password> entries=<max_users>

- Connect to the database as user SYS (or as another user with the administrative privilege).
If the user does not already exist in the database, create the user.
Grant the SYSDBA or SYSOPER system privilege to the user.
This will add the user to the password file, and that user’s name and privilege information are added to the password file.

SQL> grant sysdba to scott;

Grant succeeded.

- Confirm that the user is listed in the password file.

SQL> select * from v$pwfile_users;

USERNAME SYSDBA SYSOPER

—————————— —— ——-

SYS TRUE TRUE

SCOTT TRUE FALSE

Disable connect / as sysdba

How to disable “connect / as sysdba” ?

Do one of this step :
1. change your authentication
from SQLNET.AUTHENTICATION_SERVICES= (NTS)
to SQLNET.AUTHENTICATION_SERVICES= (BEQ,NONE)
in you sqlnet.ora if on windows.

2. remove user from the dba group

note: consider using the Password file authentication method

Unable to allocate record buffer

FRM-40900: Unable to allocate record buffer. Clear form to continue.

Cause: Failed attempt to allocate memory for a fetched or new record. The remaining records that are queried are temporarily buffered on disk. This is an indication that no more temporary files can be written to the disk.

Action: Clear form and then attempt to continue. You may have to exit the form and then re-open. Also, make sure there is enough disk space and that you have write privileges to the disk drive and directory.

————————————————-

Exit that form and try delete your temporary file then try open the same form.

Oracle Enterprise Manager Cannot Restart Database

Oracle Enterprise Manager when Restart Database:Specify Host and Target Database Credentials
has raise error message :
RemoteOperationException: ERROR: Wrong password for user

It because OEM use OS user name and password to login to target database machine
which OS user name must have right “Logon as a batch job”.
You can set this right just by

- run secpol.msc in Windows | Run
or
Start | Control Panel | Administrative Tools | Local Security Policy

- click Local Policies | User Rights Assignment

- find key ”Logon as a batch job”

- right click, choose Properties

- click button Add User or Group…

- input OS user

- that all, and try to restart database again.

^_^

ORA-06553: PLS-801: internal error [56319]

When i have finish update oracle 32-bit to 64-bit, then i try to compile procs and I got this message,

Error accessing package DBMS_APPLICATION_INFO
ERROR:
ORA-06553: PLS-801: internal error [56319]

—————————————————

ORA-00604: error occurred at recursive SQL level 2
ORA-06544: PL/SQL: internal error, arguments: [56319],[], [], [], [], [], [],[]
ORA-06553: PLS-801: internal error [56319]

i have tried steps to fix this problem
- run STANDARD.SQL to reinstall DBMS_APPLICATON_INFO
- run the DBMSUTL.SQL to create DBMS_APPLICATON_INFO
- run CATALOG.SQL,CATPPROC.SQL AND UTLPR.SQL
(sql file usually located in ORACLE_HOME/rdbms/admin)

but while running those script i got the same error.

the other steps i found on http://seilerwerks.wordpress.com/2007/03/06/fixing-a-32-to-64-bit-migration-with-utlirpsql/,

SQL> shutdown immediate;
SQL> startup upgrade;
SQL> @utlirp;

SQL> shutdown immediate;
SQL> startup;
SQL> @utlrp;

but it’s not VOILA! and errors still there laughing at me, >.<

I have search through internet and ended with answer from forum
that utlirp.sql to convert from 32 bit to 64 bit should be run when database is in migration mode.
This error is due to the 32 bit datafiles being running on a 64 bit version of oracle.

If anyone have other solution, please leave message for me. >.<

Enterprise Manager is not able to connect to the database instance

Today i got this message from OEM,

“Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.”

I have search the solution that help me to fix this problem,

- first, check DBSNMP, SYSMAN, and SYS not locked and password value is ok.

default password for DBSNMP is DBSNMP, SYSMAN is SYSMAN, SYS is MANAGER or CHANGE_ON_INSTALL.

to ensure the correct password, it is better to alter it with new password.

- emca -deconfig dbcontrol db

Database SID : <dbsid>

Listener port number : 1521 (usually)

- emca -config dbcontrol db,

Database SID : <dbsid>

Listener port number : 1521 (usually)

Password for SYS user: <SYS pwd>

Password for DBSNMP user: <DBSNMP pwd>

Password for SYSMAN user: <SYSMAN pwd>
If above step cannot resolve the problem then you can try the others,

-  C:\Documents and Settings\Administrator>set oracle_sid=<dbsid>

- C:\Documents and Settings\Administrator>emctl stop dbconsole

-  connect to database as user with DBA privilege with SQL*Plus

- SQL >alter user sysman identified by <new_password>;

- SQL >exit

- SQL >connect sysman/<new_password>;

- if connected then go to $ORACLE_HOME/host_sid/sysman/config

- locate file ”emoms.properties” and backup this file

- open and locate ”oracle.sysman.eml.mntr.emdRepPwd”, replace the encrypted value by the<new_password> value

- locate ”oracle.sysman.eml.mntr.emdRepPwdEncrypted”, replace TRUE by FALSE

- save file

- C:\Documents and Settings\Administrator>emctl start dbconsole

- if you reopen  ”emoms.properties” file, ”oracle.sysman.eml.mntr.emdRepPwd” is encrypted

and the value ”oracle.sysman.eml.mntr.emdRepPwdEncrypted” is TRUE