Hello Waqas , As explained here that for security reasons, you can no longer embed content from external domains in dashboards. To embed external content in dashboards, you must edit the instanceconfig.xml file.

Note: You can accept embedding content from all external domains or from specific domain. Each has it’s different configuration.

In case you need to embed an external content from all domains into your dashboard, so the DBA has to make the following changes in the presentation server :

• Make a backup from file ( <DOMAIN_HOME>/config/fmwconfig/biconfig/OBIPS/instanceconfig.xml ).
• Edit the original file and add the ContentSecurityPolicy element inside the Security element like below:

<ServerInstance>
...
<Security>
...
<InIFrameRenderingMode>allow</InIFrameRenderingMode>
<ContentSecurityPolicy>
<PolicyDirectives>
<Directive>
<Name>child-src</Name>
<Value>'self' www.zzz.com www.yyy.com</Value>
</Directive>
<Directive>
<Name>img-src</Name>
<Value>'self' www.zzz.com www.yyy.com</Value>
</Directive>
</PolicyDirectives>
</ContentSecurityPolicy>
...
</Security>
...
</ServerInstance>

• Save the file and restart the presentation server component (obips1).

Note: If you have notice from the configuration above there is a word (self) between single quote, this one if you didn’t specified, you will accept the external content but you will also preventing you from accessing an internal sources. So to be able to embed both external and internal you have to write this word before the domain. Also another important note that if you type * between <value>*</value> means you can embed both internal and external content inside your dashboard. in this case no need to write the word ‘self’.

Please do this on test environment first to make sure that everything is correct.

Please make sure of the credentials, because this error is quite clear enough that either the username or password is incorrect.

Note : In Oracle 11g the credentials are CASE sensitive it’s a default feature of newly oracle 11g database creation.

Now if you want to make sure whether this feature is enabled or not you can go to sqlplus then execute the following SQL command.

SHOW PARAMETER SEC_CASE_SENSITIVE_LOGON

if you get ” TRUE ” value then the the password is case sensitive otherwise it isn’t.

you can also disable this feature by executing the following SQL command :

SQL> ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

System altered.

ORA-00054 referring to the table you are trying to update it is already locked by another session that made a query for an update on the same table and not committed or rolled back yet. It could be a form or another session.

The action you could take to solve the problem is to commit or roll back the changes from the other session, causing the lock before performing the current action. There is a query also to help you identify which session that causing the lock on your table so that you can kill the session immediately.

SELECT S.USERNAME
,S.SID
,S.SERIAL#
,T.USED_UBLK
,T.USED_UREC
,RS.SEGMENT_NAME
,R.RSSIZE
,R.STATUS
FROM V$TRANSACTION T
,V$SESSION S
,V$ROLLSTAT R
,DBA_ROLLBACK_SEGS RS
WHERE S.SADDR = T.SES_ADDR
AND T.XIDUSN = R.USN
AND RS.SEGMENT_ID = T.XIDUSN
ORDER BY T.USED_UBLK DESC;

Above query has been taken from oracle-base then from the output of above query you can use SID and SERIAL# to kill the session by executing the following statement.

alter system kill session 'sid,serial#' IMMEDIATE;