Simple external job works in windows 7 enterprise but not windows 2008 R2 enterprise.

Question

SQL*Plus: Release 11.2.0.1.0
widows 7 sp1 and 2008 sp1 enterprise
The job runs without error on two  windows 7 environments but the job fails on windows 2008 with:
error 255
"EXTERNAL_LOG_ID="job_89424_68834",
ORA-27369: job of type EXECUTABLE failed with exit code: The extended attributes are inconsistent.
I know it's not the credential as I can replace it with another undefined user and it will tell me that username and/or password is not valid.
I create a specific directory with the user in question and verified I can read/write to it.
without any job arguments to cmd.exe I still get the error.
the joe can run the cmd.exe without issue.
Is there some slight difference in windows 7 and 2008 server (security?) that would account for this?
user joe  is a member of the local administrators and ora_dba groups on all servers
job and credential defined as follows:
BEGIN
    sys.dbms_scheduler.create_credential(
        username => 'joe',
        password => joespassword,
    database_role => NULL,
    windows_domain => NULL,
    comments => NULL,
    credential_name => '"DBREP"."joe"'
END;
BEGIN
    SYS.DBMS_SCHEDULER.CREATE_JOB (
            job_name => '"BLAH"."test"',
            job_type => 'EXECUTABLE',
            job_action => 'C:\Windows\System32\cmd.exe',
            number_of_arguments => 0,
            start_date => NULL,
            repeat_interval => NULL,
            end_date => NULL,
            job_class => '"SYS"."DEFAULT_JOB_CLASS"',
            enabled => FALSE,
            auto_drop => FALSE,
            comments => '',
            credential_name => '"BLAH"."joe"',
            destination_name => NULL);
        SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 1,
             argument_value => '/c');
    SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 2,
             argument_value => 'dir');
    SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 3,
             argument_value => 'c:\temp');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE(
             name => '"BLAH"."test"',
             attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_FULL);
    SYS.DBMS_SCHEDULER.enable(
             name => '"BLAH"."test"');
END;

Answer 1

Hi Andy,
It seems you're hitting the unpublished bug 12886827. The fix for this bug is included in 11.2.0.3 patch bundle 1.
Since your version is 11.2.0.1, you'll need to upgrade, which is not a bad thing anyway because 11.2.0.1 has many bugs.