A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
2 added 12 characters in body
source | link

This is a shortened, but public version of an MOS (My Oracle Support) note:

WHEN LOGIN VIA EM EXPRESS, ORA-979 IS RAISED (Doc ID 2390782.1)

Here we can find this information:

CHANGES

setting "_fix_control"='11657903:ON'

Which gives away the solution, without accessing the private content. Someone enabled the patch for bug 11657903, and that change caused this error. Try disabling the applied patch for bug 11657903:

alter session set "_fix_control"='11657903:OFF';

But this will not have any effect, as logging in to EM creates a new session. Instead of it, you can disable it at system level:

alter system set "_fix_control"='11657903:OFF';

This solves your problem, but that patch was applied to fix other issues, it is not nice to disable it completely. If you want to set a parameter dynamically, on LOGON, only for specific sessions, you can do that with a logon trigger. Here is an example of such a trigger that shows you how to set _fix_control for a specific user and patch, just change it to your needs.

http://karandba.blogspot.com/2015/03/tracing-session-with-client-identifier.html

CREATE OR REPLACE TRIGGER set_trace_logon_test1
AFTER LOGON ON SCOTT.SCHEMA
WHEN (lower(sys_context('USERENV', 'CLIENT_IDENTIFIER')) like '%hr%')
DECLARE
lcommand varchar(200);
BEGIN
EXECUTE IMMEDIATE 'alter session set tracefile_identifier=''From_Trigger''';
EXECUTE IMMEDIATE 'alter session set statistics_level=ALL';
EXECUTE IMMEDIATE 'alter session set max_dump_file_size=UNLIMITED';
EXECUTE IMMEDIATE 'alter session set events ''10046 trace name context forever, level 12 : 10053 trace name context forever, level 1''';
EXECUTE IMMEDIATE 'alter session set "_fix_control"="6765823:off"';
insert into sys.trigger_test values (sys_context('USERENV', 'CLIENT_IDENTIFIER'),sysdate,'LOGON');
commit;
END set_trace_logon_test1;
/

This is a shortened, but public version of an MOS (My Oracle Support) note:

WHEN LOGIN VIA EM EXPRESS, ORA-979 IS RAISED (Doc ID 2390782.1)

Here we can find this information:

CHANGES

setting "_fix_control"='11657903:ON'

Which gives away the solution, without accessing the private content. Someone enabled the patch for bug 11657903 that caused this error. Try disabling the applied patch for bug 11657903:

alter session set "_fix_control"='11657903:OFF';

But this will not have any effect, as logging in to EM creates a new session. Instead of it, you can disable it at system level:

alter system set "_fix_control"='11657903:OFF';

This solves your problem, but that patch was applied to fix other issues, it is not nice to disable it completely. If you want to set a parameter dynamically, on LOGON, only for specific sessions, you can do that with a logon trigger. Here is an example of such a trigger that shows you how to set _fix_control for a specific user and patch, just change it to your needs.

http://karandba.blogspot.com/2015/03/tracing-session-with-client-identifier.html

CREATE OR REPLACE TRIGGER set_trace_logon_test1
AFTER LOGON ON SCOTT.SCHEMA
WHEN (lower(sys_context('USERENV', 'CLIENT_IDENTIFIER')) like '%hr%')
DECLARE
lcommand varchar(200);
BEGIN
EXECUTE IMMEDIATE 'alter session set tracefile_identifier=''From_Trigger''';
EXECUTE IMMEDIATE 'alter session set statistics_level=ALL';
EXECUTE IMMEDIATE 'alter session set max_dump_file_size=UNLIMITED';
EXECUTE IMMEDIATE 'alter session set events ''10046 trace name context forever, level 12 : 10053 trace name context forever, level 1''';
EXECUTE IMMEDIATE 'alter session set "_fix_control"="6765823:off"';
insert into sys.trigger_test values (sys_context('USERENV', 'CLIENT_IDENTIFIER'),sysdate,'LOGON');
commit;
END set_trace_logon_test1;
/

This is a shortened, but public version of an MOS (My Oracle Support) note:

WHEN LOGIN VIA EM EXPRESS, ORA-979 IS RAISED (Doc ID 2390782.1)

Here we can find this information:

CHANGES

setting "_fix_control"='11657903:ON'

Which gives away the solution, without accessing the private content. Someone enabled the patch for bug 11657903, and that change caused this error. Try disabling the applied patch for bug 11657903:

alter session set "_fix_control"='11657903:OFF';

But this will not have any effect, as logging in to EM creates a new session. Instead of it, you can disable it at system level:

alter system set "_fix_control"='11657903:OFF';

This solves your problem, but that patch was applied to fix other issues, it is not nice to disable it completely. If you want to set a parameter dynamically, on LOGON, only for specific sessions, you can do that with a logon trigger. Here is an example of such a trigger that shows you how to set _fix_control for a specific user and patch, just change it to your needs.

http://karandba.blogspot.com/2015/03/tracing-session-with-client-identifier.html

CREATE OR REPLACE TRIGGER set_trace_logon_test1
AFTER LOGON ON SCOTT.SCHEMA
WHEN (lower(sys_context('USERENV', 'CLIENT_IDENTIFIER')) like '%hr%')
DECLARE
lcommand varchar(200);
BEGIN
EXECUTE IMMEDIATE 'alter session set tracefile_identifier=''From_Trigger''';
EXECUTE IMMEDIATE 'alter session set statistics_level=ALL';
EXECUTE IMMEDIATE 'alter session set max_dump_file_size=UNLIMITED';
EXECUTE IMMEDIATE 'alter session set events ''10046 trace name context forever, level 12 : 10053 trace name context forever, level 1''';
EXECUTE IMMEDIATE 'alter session set "_fix_control"="6765823:off"';
insert into sys.trigger_test values (sys_context('USERENV', 'CLIENT_IDENTIFIER'),sysdate,'LOGON');
commit;
END set_trace_logon_test1;
/
1
source | link

This is a shortened, but public version of an MOS (My Oracle Support) note:

WHEN LOGIN VIA EM EXPRESS, ORA-979 IS RAISED (Doc ID 2390782.1)

Here we can find this information:

CHANGES

setting "_fix_control"='11657903:ON'

Which gives away the solution, without accessing the private content. Someone enabled the patch for bug 11657903 that caused this error. Try disabling the applied patch for bug 11657903:

alter session set "_fix_control"='11657903:OFF';

But this will not have any effect, as logging in to EM creates a new session. Instead of it, you can disable it at system level:

alter system set "_fix_control"='11657903:OFF';

This solves your problem, but that patch was applied to fix other issues, it is not nice to disable it completely. If you want to set a parameter dynamically, on LOGON, only for specific sessions, you can do that with a logon trigger. Here is an example of such a trigger that shows you how to set _fix_control for a specific user and patch, just change it to your needs.

http://karandba.blogspot.com/2015/03/tracing-session-with-client-identifier.html

CREATE OR REPLACE TRIGGER set_trace_logon_test1
AFTER LOGON ON SCOTT.SCHEMA
WHEN (lower(sys_context('USERENV', 'CLIENT_IDENTIFIER')) like '%hr%')
DECLARE
lcommand varchar(200);
BEGIN
EXECUTE IMMEDIATE 'alter session set tracefile_identifier=''From_Trigger''';
EXECUTE IMMEDIATE 'alter session set statistics_level=ALL';
EXECUTE IMMEDIATE 'alter session set max_dump_file_size=UNLIMITED';
EXECUTE IMMEDIATE 'alter session set events ''10046 trace name context forever, level 12 : 10053 trace name context forever, level 1''';
EXECUTE IMMEDIATE 'alter session set "_fix_control"="6765823:off"';
insert into sys.trigger_test values (sys_context('USERENV', 'CLIENT_IDENTIFIER'),sysdate,'LOGON');
commit;
END set_trace_logon_test1;
/