Today Jayabharath Velugoti pinged me, about forms not launching in an 11i instance. When I tried reproducing the issue, I go this in my laptop java console:
Following Exception occured: java.lang.IllegalArgumentException: Illegal argument for colorScheme applet parameter
java.lang.IllegalArgumentException: Illegal argument for colorScheme applet parameter
at oracle.forms.engine.Main.initDesktop(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
A search on support.oracle.com revealed this article: Opening Any Form Applications Gives: Illegal Argument For Color Scheme Applet Parameter. [ID 858367.1]
However this article was relevant to R12. Anyhow, I executed the query given in the article:
col NAME for a25
col LEV for a4
col CONTEXT for a30
col VALUE for a12
select po.profile_option_name "NAME",
decode(to_char(pov.level_id),
'10001', 'SITE',
'10002', 'APP',
'10003', 'RESP',
'10004', 'USER', '???') "LEV",
decode(to_char(pov.level_id),
'10001', '',
'10002', app.application_short_name,
'10003', rsp.responsibility_key,
'10004', usr.user_name,
'???') "CONTEXT",
pov.profile_option_value "VALUE"
from FND_PROFILE_OPTIONS po,
FND_PROFILE_OPTION_VALUES pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp
where po.profile_option_name like 'FND_COLOR_SCHEME'
and pov.application_id = po.application_id
and pov.profile_option_id = po.profile_option_id
and usr.user_id (+) = pov.level_value
and rsp.application_id (+) = pov.level_value_application_id
and rsp.responsibility_id (+) = pov.level_value
and app.application_id (+) = pov.level_value
order by "NAME", pov.level_id, "VALUE"
NAME LEV CONTEXT VALUE
------------------------- ---- ------------------------------ ------------
FND_COLOR_SCHEME SITE SWAN
FND_COLOR_SCHEME USER JOHNDOE SWAN
FND_COLOR_SCHEME USER JANEDOE SWAN
That didn't look right. This is an 11i instance. Swan interface is a new feature introduced in R12. So I asked Jayabharath about it and he said that this instance was an R12 instance and was recently cloned again as an 11i instance. That doesn't explain it as the source 11i instance didn't have SWAN. Possibly, someone did this by mistake. Anyways, I updated the values from SWAN to BLUE: SQL> Declare
value Boolean;
Begin
value := fnd_profile.save('FND_COLOR_SCHEME','BLUE','SITE');
End;
/
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> UPDATE FND_PROFILE_OPTION_VALUES
2 SET PROFILE_OPTION_VALUE='BLUE'
3 WHERE PROFILE_OPTION_VALUE='SWAN';
2 rows updated.
SQL> COMMIT;
The query showed BLUE now:
NAME LEV CONTEXT VALUE
------------------------ ---- ------------------------------ ------------
FND_COLOR_SCHEME SITE BLUE
FND_COLOR_SCHEME USER JOHNDOE BLUE
FND_COLOR_SCHEME USER JANEDOE BLUE
Apache was bounced, and forms launched fine without this issue.
Following Exception occured: java.lang.IllegalArgumentException: Illegal argument for colorScheme applet parameter
java.lang.IllegalArgumentException: Illegal argument for colorScheme applet parameter
at oracle.forms.engine.Main.initDesktop(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
A search on support.oracle.com revealed this article: Opening Any Form Applications Gives: Illegal Argument For Color Scheme Applet Parameter. [ID 858367.1]
However this article was relevant to R12. Anyhow, I executed the query given in the article:
col NAME for a25
col LEV for a4
col CONTEXT for a30
col VALUE for a12
select po.profile_option_name "NAME",
decode(to_char(pov.level_id),
'10001', 'SITE',
'10002', 'APP',
'10003', 'RESP',
'10004', 'USER', '???') "LEV",
decode(to_char(pov.level_id),
'10001', '',
'10002', app.application_short_name,
'10003', rsp.responsibility_key,
'10004', usr.user_name,
'???') "CONTEXT",
pov.profile_option_value "VALUE"
from FND_PROFILE_OPTIONS po,
FND_PROFILE_OPTION_VALUES pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp
where po.profile_option_name like 'FND_COLOR_SCHEME'
and pov.application_id = po.application_id
and pov.profile_option_id = po.profile_option_id
and usr.user_id (+) = pov.level_value
and rsp.application_id (+) = pov.level_value_application_id
and rsp.responsibility_id (+) = pov.level_value
and app.application_id (+) = pov.level_value
order by "NAME", pov.level_id, "VALUE"
NAME LEV CONTEXT VALUE
------------------------- ---- ------------------------------ ------------
FND_COLOR_SCHEME SITE SWAN
FND_COLOR_SCHEME USER JOHNDOE SWAN
FND_COLOR_SCHEME USER JANEDOE SWAN
That didn't look right. This is an 11i instance. Swan interface is a new feature introduced in R12. So I asked Jayabharath about it and he said that this instance was an R12 instance and was recently cloned again as an 11i instance. That doesn't explain it as the source 11i instance didn't have SWAN. Possibly, someone did this by mistake. Anyways, I updated the values from SWAN to BLUE: SQL> Declare
value Boolean;
Begin
value := fnd_profile.save('FND_COLOR_SCHEME','BLUE','SITE');
End;
/
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> UPDATE FND_PROFILE_OPTION_VALUES
2 SET PROFILE_OPTION_VALUE='BLUE'
3 WHERE PROFILE_OPTION_VALUE='SWAN';
2 rows updated.
SQL> COMMIT;
The query showed BLUE now:
NAME LEV CONTEXT VALUE
------------------------ ---- ------------------------------ ------------
FND_COLOR_SCHEME SITE BLUE
FND_COLOR_SCHEME USER JOHNDOE BLUE
FND_COLOR_SCHEME USER JANEDOE BLUE
Apache was bounced, and forms launched fine without this issue.
No comments:
Post a Comment