Check Out

I could have created the item manually across all the applications, but being a programmer brain plus lazy butt, I don’t wanted to give up.

I did following and it worked more than fine to me.

I navigate to “Share Components” Page of source Application

On the right hand side under “Tasks”, I selected “Export Application Components”

Exported only the ” Application Items”

Save the file as “f110_components.SQL”

Open the file in notepad

Changed following three things depending on the target application number and workspace.

Get the Workspace ID using following SQL at your target and note down the Workspace ID.
“select WORKSPACE_ID from APEX_WORKSPACES”

Search for following function in the file:
wwv_flow_api.set_security_group_id

Change it using following syntax
wwv_flow_api.set_security_group_id(p_security_group_id=>OB_WORKSPACE_ID);

Where OB_WORKSPACE_ID is Workspace ID

example in my case it was “5622003592886707″ so I changes as follows:
wwv_flow_api.set_security_group_id(p_security_group_id=>5622003592886707);

The search for the line where following variable is being initialized
wwv_flow.g_flow_id

Change it using following syntax
wwv_flow.g_flow_id := OB_APPLICATION_ID;

Where OB_APPLICATION_ID is the Application ID or you can say Application Number

In my case it was 136 I changed it as follows:
wwv_flow.g_flow_id := 136;

Hint: Application Express always shows Application ID beside your application name.

The search for the line where following variable is being initialized
wwv_flow_api.g_id_offset

Change it using following syntax
wwv_flow_api.g_id_offset := OB_RANDOM_NUMBER;

Where OB_RANDOM_NUMBER is any random INTEGER other than zero

Script Before Change:
……….
…..
prompt  Set Credentials…

begin

– Assumes you are running the script connected to SQL*Plus as the Oracle user APEX_030200 or as the owner (parsing schema) of the application.
wwv_flow_api.set_security_group_id(p_security_group_id=>1122003592886707);

end;
/
…..
……

prompt  Set Application ID…

begin

– SET APPLICATION ID
wwv_flow.g_flow_id := 110;
wwv_flow_api.g_id_offset := 0;
null;

end;
/
……
……

Script After Change:
……….
…..
prompt  Set Credentials…

begin

– Assumes you are running the script connected to SQL*Plus as the Oracle user APEX_030200 or as the owner (parsing schema) of the application.
wwv_flow_api.set_security_group_id(p_security_group_id=>5622003592886707);

end;
/
…..
……

prompt  Set Application ID…

begin

– SET APPLICATION ID
wwv_flow.g_flow_id := 136;
wwv_flow_api.g_id_offset := 1;
null;

end;
/
……
……

After that imported into my target application without any error.

hope this will help somebody!

I think so…….

Any way let me explain the situation and how I tackle it.

Lets assume there are two database one is prod (live one) and another one dev (development).

There came a request from one non oracle developer that he want to have a readonly access to the “production_note” table in prod database as he wanted to access live data of “production_note” table.

In normal situation if it was development environment then I would have done following:

Login into SQL*Plus as SYSTEM in “prod” database

SQL> connect system/system@biz11
Connected.

SQL> create user production identified by production default tablespace users;

User created.

SQL> grant connect, resource to production;

Grant succeeded.

SQL> connect actual_user/actual_user@biz11
Connected.

SQL> grant select on production_notes to production;

Grant succeeded.

SQL> connect production/production@biz11
Connected.

SQL> create synonym production_notes for actual_user.production_notes;

Synonym created.

Then give him access to this new user.

But now here situation is different.I have security by IP addresses in “prod” database. Only Oracle Application Server and “dev” database server can access the  “prod” database and I don’t want to give access to IP address of this developer’s machine. If I do so it might open some loop hole in security infra of my client.

So to tackle this situation I did as follows:

First I did same as above in “Prod” database.

Then I Login into SQL*Plus as SYSTEM in “dev” database

SQL>CREATE PUBLIC DATABASE LINK prod_remote
2     CONNECT TO production IDENTIFIED BY production
3     USING ‘biz11′;

Database link created.

SQL> create user production identified by production default tablespace users;

User created.

SQL> grant connect, resource to production;

Grant succeeded.

SQL> CREATE SYNONYM production_notes
2     FOR production.production_notes@prod_remote;

Synonym created.

Then I just gave him access to this new user in “dev” database without making things complicated for this non oracle user.

Thats it, Mission Accomplished

I hope this post will help somebody and offcourse me as a reference material for future!

Error is displayed as follows:
ORA-20001: The printing engine could not be reached because either the URL specified is incorrect or a proxy URL needs to be specified.

Actually this happens due to security related enhancement done in Oracle Database 11g release 1.

Now starting with Oracle Database 11g,  by default, the ability to interact with network services is disabled in Oracle Database.

If you want to enable it for certain host or user then you need to use the new DBMS_NETWORK_ACL_ADMIN package to grant connect privileges to them.

So here too we need to grant connect privilege to APEX_030200 apex database user as follows:

DECLARE
ACL_PATH  VARCHAR2(4000);
ACL_ID    RAW(16);
BEGIN
SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
WHERE HOST = ‘*’ AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

SELECT SYS_OP_R2O(extractValue(P.RES, ‘/Resource/XMLRef’)) INTO ACL_ID
FROM XDB.XDB$ACL A, PATH_VIEW P
WHERE extractValue(P.RES, ‘/Resource/XMLRef’) = REF(A) AND
EQUALS_PATH(P.RES, ACL_PATH) = 1;

DBMS_XDBZ.ValidateACL(ACL_ID);
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, ‘APEX_030200‘,
‘connect’) IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
‘APEX_030200‘, TRUE, ‘connect’);
END IF;

EXCEPTION

WHEN NO_DATA_FOUND THEN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL(’power_users.xml’,
‘ACL that lets power users to connect to everywhere’,
‘APEX_030200′, TRUE, ‘connect’);
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL(’power_users.xml’,'*’);
END;

COMMIT;

Please refer Oracle Documentation page for more details.

I have simply replaced FLOWS_030100 with APEX_030200.

Thing to Notice: Starting Application Express 3.2.0.00.27, the Application Express Database user is prefix APEX_ instead of FLOWS_.

Hope this post will help others!

For example I wanted to run sql “select * from tab”
When I checked “Autocommit” checkbox, it worked fine as follows:

But when I unchecked the “Autocommit” checkbox it gave me following error:
ORA-01003: no statement parsed

Oracle hasn’t made it available for download, but they have made it available in their hosted development site.

Get details on feature notes here

When I first read the news I couldn’t believe it…..

My tearful homage to Carl Backstrom, who left for heavenly abode on October 26, 2008.

I don’t know Carl personally but his work in Oracle Application Express have always inspires me for new ideas and helped me in difficult situations.

May the Lord grant everlasting peace to his soul.

My deepest condolences to Carl’s daughter ,Destany, and all his family members.
Carl’s Memorial Fund has been setup by Carl’s friends which will be set aside to send his daughter, Destany, to college to ensure she has the future Carl dreamed for her.

Donations to Carl’s Memorial Fund can be made several ways:

Domestic wire transfers
Account Number 152460903
Citibank ABA Number 322271724

International wire transfers SWIFT Code: CITI US 33

Checks
Make payable to Susan Bailey (Carl’s Mother)
Address: 3395 S. Jones Blvd #403
Las Vegas, NV 89146

May All Your Wishes Come True And Lead You Into The Path of Continued Success, Prosperity, Good Health and Never Ending Happiness……

When I checked my alter log It showed me as follows:

After that I checked parameter file which showed me value of undo tablespace as follows:

After this I change the name in my create database script same as above i.e. “UNDOTBS”. Once done the database was created without any error.

I hope this will help out somebody!

Everything ran smooth and I was able to run my forms and do transaction and so on.

But the problem started when I tried to run reports. When ever I try running any report, it failed and gave me error that it unable to connect to the database.

I was scratching my head where exactly I am going wrong.

When my forms server can connect the database with same setting from conf file then why report server is giving error.

After checking the log and trace file I got following:

REP-501: Unable to connect to the specified database.
[2008/9/27 2:38:28:240] Debug 50103 (JobManager:notifyWaitingJobs): Master job 76257 notify its duplicated jobs.
[2008/9/27 2:38:28:240] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 76257
[2008/9/27 2:38:28:240] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Ready
[2008/9/27 2:38:28:240] Exception 501 (): Unable to connect to the specified database.
exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=501,
java.lang.String errorString=”Unable to connect to the specified database.”,
java.lang.String moduleName=”REP”
}}
}

I don’t remember setting any other database setting for the reports.

After 4-5 hours of doing my investigation and going around in googling, checking trace and log files again and again.

At last I got to know following fact:

By default, Username and Password are passed to Reports from Forms are in upper case

Bang I was knocked off……………..

Later I found two solutions given by Oracle for this problem as follows:

Solution 1

For forms 10g release 1 or less
Disable Password Case Sensitivity in Oracle 11g
set the SEC_CASE_SENSITIVE_LOGON initialization parameter to FALSE and restart the database.

Solution 2
For forms 10g release 1 ( with Patch 4399342) or above
Add the variable: FORMS_USERNAME_CASESENSITIVE = 1, in application environment file
([ORACLE_HOME/forms/server/default.env] or any custom envFile)

I went for solution 1 as my forms and reports are in 10g Release 1 (without Patch 4399342)

That was great relief and was my time to sleep.

So wished the Good Morning to my Laptop and went for slumber!