Owb job (import) scheduling with oem 2.2

Hi all,
System config :
oracle 8.1.7 enterprise, oem 2.2.0.0.0 and owb 3i. on
windows nt workstation.
I created necessary source and target module and mapping is
completed in owb. When I generated scripts on mapped objects,
it created a ctl script and tcl scripts. when I try to register
with OEM register it is giving following error message
"failed to register the jobs with oem. oem registratrion failed.
please make sure you have oem client installed locally. the oem
is running and you have enter informationa oem inforamtion under
preferences".
But actually oem is running on my system, oracle8ihomeagent
is running and other things are also fine.
Can any one help me in addressing the problem.
Thanks a lot.
with regards
sreenivas

As bazzza mentioned, try a simple SQL script with say "select 1 from dual".
What is the RMAN Script doing? A big Backup? If it has not failed with an error, then check from the database to see if the session is doing something.

Similar Messages

  • JOB's Schedule Table

    From Which Table we can know which Jobs are Schedule with Variants....

    Hi Abhishek,
    1. TBTCO
       Header table.
    2. TBTCP
       It contains the STEPS (program names)
       with varaint.
    3 See package SBTC
       T* tables.
    Regards,
    Amit M.
    Message was edited by: Amit Mittal
    Message was edited by: Amit Mittal

  • Schedule FTP Job with OEM 9i

    Hi All,
    Does anyone have experience of setting schedule ftp job with OEM and could give me some hints or an example, thank you very much. I am now using Oracle 9i.
    Rds,
    CH

    Lucas,
    Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
    Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
    Hope this helps,
    Mark.

  • Registering OWB jobs with OEM

    We are facing the problem of OWB job registration in OEM. The error message that we are getting is
    " Failed to register the jobs with OEM: OEM Registration Failed. Please make sure you have OEM client Installed locally, thee Oracle Management Server is running, and you have entered correct connection information and OEM information under 'Preferences'.
    Error in initializing the service. Please enter correct OMS domain name in the configuration parameter and make sure that the OMS is running.
    Oracle.sysman.emSDK.client.omsclientVersionMismatchException: Unable to connect to the Management server ind-spz7w2s0055.com. The management server version 9.2.0.1.0 Production is incompatible with this client 9.0
    Job object failed to create, check to see if user has credentials."
    The above mentioned paragraph is a single error message that we are getting.
    We have referred to following documents at Metalink site:
    Doc ID : Note 1081184.6
    Doc ID : Note 124011.1
    Doc ID : Note 169922.1
    . We have also installed the patch 9.0.2.66.0. but problem continues.
    Please help.

    Lucas,
    Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
    Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
    Hope this helps,
    Mark.

  • Registering LOAD job with OEM fails

    I tried to register a Mapping from a flat file to a table (SQL*Loader job) from OWB 9i (9.0.3) to OEM (9.2). This worked fine. However, the job failed to run because as the output states: the controlfile is not passed. And I can see that it is not among the job parameters.
    How can it be that the standard job registering process does not include that essential parameter?
    Is there a way to get a data load job properly defined in OEM?
    Why is this job scheduled as a TCL job and not as a LOAD job?
    thanks very much for any input!
    Lucas

    Lucas,
    Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
    Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
    Hope this helps,
    Mark.

  • Creating a job and scheduling a job error in OEM

    Hi, Everyone,
    I am trying to create and schedule a job thru OEM. In the the pl/sql block provide i have given my code like this
    begin
    SET SERVEROUTPUT ON;
    SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND;
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
    EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
    SPOOL OFF;
    end;
    i have created the job and scheduled it but i am getting this error:
    Error # 6550
    Details ORA-06550: line 2, column 5: PL/SQL: ORA-00922: missing or invalid option ORA-06550: line 2, column 1: PL/SQL: SQL Statement ignored ORA-06550: line 3, column 7: PLS-00103: Encountered the symbol "C" when expecting one of the following: := . ( @ % ;
    could anyone pls help as this is very urgent.
    Thanks in advance

    Ah, the problem is you are confusing SQLPlus commands with PL/SQL.
    SET SERVEROUTPUT ON; -- This is a SQLPlus command, not necessary here.
    SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND; -- This is a SQLPlus command, in PL/SQL to write out to a file you will need to call the UTL_FILE package to open a file for writing to. Except that the file you write to will appear on the database server, not your workstation, when the scheduled job runs.
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL; -- In PL/SQL you need to SELECT columns INTO variables FROM tables. But in fact I guess you want to write the time to file using UTL_FILE again. However, you don't really need to do this, since scheduler will log the start time and run duration itself.
    EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910); -- This is the SQLPlus equivalent of the PL/SQL command:
    BEGIN
    PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    END;
    SPOOL OFF; -- This is a SQLPlus command, not necessary here.
    So to summarise, all you really need is:
    BEGIN
    PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    END;
    And the scheduled job will log the start time and duration in the database, which you can find here:
    SELECT * FROM USER_SCHEDULER_JOB_RUN_DETAILS

  • Fail to register the jobs with OEM

    I have done following steps in developing a data warehouse project but im still in problum to load data from source to target:
    Create a source object with thier tables
    create a target object a dimension
    create a mapping
    create to operator one for source table and other for dimension
    linked colum by column
    validate this mapping
    genrate this mapping
    deployed this mapping
    but i am facing problum while i am goining to register the TCL with OEM. I am unable to register this and following error occures
    Faild to register the jobs with OEM:OEM registration Faild: OEM client not installed in Oracle_Home.
    java.lang.NoClassDefFoundError.
    Oracle/sysman/enSDK/client/omsClient/BadAttributeException
    Exception in thread "main"
    Plz help me to solve this problum.
    Plz give me exact solution.
    Plz give me steps from start to end of a data warehouse project.Steps involves in design ,validate and genrate and loading phase plz give me list of these steps.

    This combination is not certified. Please upgrade OWB to the latest available version (9.0.3.35) that is certified on the 9.2.0.1 database.
    Regards:
    Igor

  • How to run an OWB 11gR2 process flow using OEMS Jobs?

    How to run an OWB 11gR2 process flow using OEMS 11g Jobs?
    In other words iam trying to create an Oracle Enterprise manager job for scheduling and running an OWB Process flow.
    Can any one of you please route me to a documentation for the same,or enlist the steps involved?

    Hi,
    look at OWB API Reference (it is of 11gR1 OWB release but you can apply this procedure to OWB11gR2 as well)
    http://download.oracle.com/docs/cd/B28359_01/owb.111/b31279/api_4sqlforjobs.htm#BABEBGHA
    Regards,
    oleg

  • Scheduling thru OEM 10g

    Hi,
    would anybody tell me how to schedule the jobs like OWB Mappings/Process Flows thru OEM 10g.
    Thanks in Advance.
    Ashish

    Are you familiar with the oem_exec_template.sql file? This is provided with OWB in the following directory: <OWB_HOME>/rtp/sql.
    This will allow you to execute mappings or process flows from SQLPlus. There are a number of parameters required. There is plenty of documentation at the beginning of the file defining each of the parameters. Using this, you can schedule process flows in 10g R1. I am currently doing this and it seems to work quite well with the exception of a few unrelated issues.
    Hoe this helps.
    John

  • WorkFlow OWB Jobs

    Is there a way to run the Workflow jobs independent of Oracle clients (OWB and OEM)? We currently have OWB client for windows installed on our machine and cannot use windows to run our jobs in our production environment. Is there a way to run OWB jobs in unix?

    Hi,
    Assuming the 3 users/schemas after the OWB installations are owb,owbuser,owbrun(runtime)
    Login with Owbuser ID/pwd to Unix sqlplus
    then execute the following line (all in one line)
    @/build/owb92/owb/rtp/sql/oem_exec_template.sql owbrun CDS_TXN_LOAD_PROCESS_FLOW_LOC PROCESS CDS_TXN_LOAD_PROCESS_FLOW_01 "," ","
    where
    @/build/owb92/owb/rtp/sql/oem_exec_template.sql - complete path of oem_exec_template.sql file
    CDS_TXN_LOAD_PROCESS_FLOW_LOC - process flow location
    CDS_TXN_LOAD_PROCESS_FLOW_01 - process flow name
    PROCESS - keyword to run workflow process
    Cheers
    Ranjeesh

  • Error while adding a job to scheduler

    Hello,
    I have a batch job that is running fine in both DEV and QA environment. In DEV, I am able to schedule and run it daily. I created a similar schedule in QA environment using BODS Mgmt Console/Administrator. However, upon Activating the schedule, I am getting the following error message. Would someone know why would this error be thrown and steps to troubleshoot this error?
    Thanks.
    [Repository:AECON_DW_REPOSITORY Schedule:Daily_Run_QA Error:Error while adding a job to scheduler]
    When contacting the server above exception was encountered, so it will be assumed the schedule is not active anymore.

    Hi Rizwan Tahir  ,
    Delete the job server associated with the current batch job and recreate it.
    Then try creating a new schedule using the new job server.
    And take care that job server is created in QA environment.
    Hope this should work.
    Regards,

  • Guide to External Jobs on 10g with dbms_scheduler e.g. scripts,batch files

    GUIDE TO RUNNING EXTERNAL JOBS ON 10g WITH DBMS_SCHEDULER
    NOTE: Users using 11g should use the new method of specifying a credential which eliminates many of the issues mentioned in this note.
    This guide covers several common questions and problems encountered when using
    dbms_scheduler to run external jobs, either on Windows or on UNIX.
    What operating system (OS) user does the job run as ?
    External jobs which have a credential (available in 11g) run as the user
    specified in the credential. But for jobs without credentials including
    all jobs in 10gR1 and 10gR2 there are several cases.
    - On UNIX systems, in releases including and after 10.2.0.2 there is a file $ORACLE_HOME/rdbms/admin/externaljob.ora . All external jobs not in the SYS schema and with no credential run as the user and group specified in this file. This should be nobody:nobody by default.
    - On UNIX systems, in releases prior to 10.2.0.2 there was no "externaljob.ora" file. In this case all external jobs not in the SYS schema and with no credential run as the owner and group of the $ORACLE_HOME/bin/extjob file which should be setuid and setgid. By default extjob is owned by nobody:nobody except for oracle-xe where it is owned by oracle:oraclegroup and is not setuid/setgid.
    - On Windows, external jobs not in the SYS schema and with no credential run as the user that the OracleJobScheduler Windows service runs as. This service must be started before these jobs can run.
    - In all releases on both Windows and UNIX systems, external jobs in the SYS schema without a credential run as the oracle user.
    What errors are reported in SCHEDULERJOB_RUN_DETAILS views ?
    If a job fails, the first place to look for diagnostic information is the SCHEDULERJOB_RUN_DETAILS set of views. In 10gR2 and up the first 200 characters of the standard error stream is included in the additional_info column.
    In all releases, the error number returned by the job is converted into a
    system error message (e.g. errno.h on UNIX or net helpmsg on Windows) and that
    system error message is recorded in the additional info column. If there is no
    corresponding message the number is displayed.
    In 11g and up the error number returned by the job is additionally recorded in
    the error# column. In earlier releases 27369 would always be recorded in the
    error# column.
    Generic Issues Applicable to UNIX and Windows
    - The job action (script or executable) must return 0 or the job run will be marked as failed.
    - Always use the full pathname to executables and scripts.
    - Do not count on environment variables being set in your job. Make sure that the script or executable that your jobs runs sets all required environment variables including ORACLE_HOME, ORACLE_SID, PATH etc.
    - It is not recommended to pass in a complete command line including arguments as the action. Instead it is recommended to pass in only the path to and name of the executable and to pass in arguments as job argument values.
    - Scripts with special characters in the execution path or script name may give problems.
    - Ensure that the OS user your job runs as has the required privileges/permissions to run your job. See above for how to tell who the job runs as.
    - External job actions cannot contain redirection operators e.g. > < >> | && ||
    - In general try getting a simple external job working first e.g. /bin/echo or ipconfig.exe on Windows. Also try running the job action directly from the commandline as the OS user that the job will run as.
    Windows-specific Issues
    - The OracleJobScheduler Windows service must be started before external jobs will run (except for jobs in the SYS schema and jobs with credentials).
    - The user that the OracleJobScheduler Windows service runs as must have the "Log on as batch job" Windows privilege.
    - A batch file (ending in .bat) cannot be called directly by the Scheduler. Instead cmd.exe must be used and the name of the batch file passed in as an argument. For example
    begin
    dbms_scheduler.create_job('myjob',
       job_action=>'C:\WINDOWS\SYSTEM32\CMD.EXE',
       number_of_arguments=>3,
       job_type=>'executable', enabled=>false);
    dbms_scheduler.set_job_argument_value('myjob',1,'/q');
    dbms_scheduler.set_job_argument_value('myjob',2,'/c');
    dbms_scheduler.set_job_argument_value('myjob',3,'c:\temp\test.bat');
    dbms_scheduler.enable('myjob');
    end;
    /- In 10gR1 external jobs that wrote to standard output or standard error streams would sometimes return errors. Redirect to files or suppress all output and error messages when using 10gR1 to run external jobs.
    UNIX-specific Issues
    - When running scripts, make sure that the executable bit is set.
    - When running scripts directly, make sure that the first line of the script in a valid shebang line - starting with "#!" and containing the interpreter for the script.
    - In release 10.2.0.1, jobs creating a large amount of standard error text may hang when running (this was fixed in the first 10.2.0.2 patchset). If you are seeing this issue, redirect standard error to a file in your job. This issue has been seen when running the expdp utility which may produce large amounts of standard error text.
    - the user that the job runs as (see above section) must have execute access on $ORACLE_HOME/bin and all parent directories. If this is not the case the job may be reported as failed or hang in a running state. For example if your $ORACLE_HOME is /opt/oracle/db then you would have to make sure that
    chmod a+rx /opt
    chmod a+rx /opt/oracle
    chmod a+rx /opt/oracle/db
    chmod a+rx /opt/oracle/db/bin
    - On oracle-xe, the primary group of your oracle user (if it exists) must be dba before you install oracle-xe for external jobs to work. If you have an oracle user from a regular Oracle installation it may have the primary group set to oinstall.
    - On oracle-xe, the extjobo executable is missing so external jobs in the SYS schema will not work properly. This can be fixed by copying the extjob executable to extjobo in the same directory ($ORACLE_HOME/bin).
    - Check that correct permissions are set for external job files - extjob and externaljob.ora (see below)
    Correct permissions for extjob and externaljob.ora on UNIX
    There is some confusion as to what correct permissions are for external job related files.
    In 10gR1 and 10.2.0.1 :
    - rdbms/admin/externaljob.ora should not exist
    - bin/extjob should be setuid and setgid 6550 (r-sr-s---). It should be owned by the user that jobs should run as and by the group that jobs should run as.
    - bin/extjobo should have normal 755 (rwxr-xr-x) permissions and be owned by oracle:oraclegroup
    In 10.2.0.2 and higher
    - rdbms/admin/externaljob.ora file must must be owned by root:oraclegroup and be writable only by the owner i.e. 644 (rw-r--r--) It must contain at least two lines: one specifying the run-user and one specifying the run-group.
    - bin/extjob file must be also owned by root:oraclegroup but must be setuid i.e. 4750 (-rwsr-x---)
    - bin/extjobo should have normal 755 (rwxr-xr-x) permissions and be owned by oracle:oraclegroup
    In 11g and higher
    Same as 10.2.0.2 but additionally bin/jssu should exist with root setuid
    permissions i.e. owned by root:oraclegroup with 4750 (-rwsr-x---)
    Internal Error numbers for UNIX on 10.2.0.2 or 10.1.0.6 or higher
    If you are not using a credential and are using version 10.2.0.2 or higher or 10.1.0.6 or higher you may come across an internal error number. Here are the meanings for the internal error numbers.
    274661 - can't get owner of or permissions of externaljob.ora file
    274662 - not running as root or externaljob.ora file is writable by group or other or externaljob.ora file not owned by root (can't switch user)
    274663 - setting the group or effective group failed
    274664 - setting the user or effective user failed
    274665 - a user or group id was not changed successfully
    274666 - cannot access or open externaljob.ora file
    274667 - invalid run_user specified in externaljob.ora file
    274668 - invalid run_group specified in externaljob.ora file
    274669 - error parsing externaljob.ora file
    274670 - extjobo is running as root user or group

    Hi Ravi,
    Can you help me...
    Hi All,
    I planned to create a job to do rman backup daily at 04:00 AM.
    1. I created a program as follows
    BEGIN
    DBMS_SCHEDULER.CREATE_PROGRAM(
    program_name => 'rman_backup_prg',
    program_action => '/u02/rmanback/rman.sh',
    program_type => 'EXECUTABLE',
    comments => 'RMAN BACKUP');
    END;
    my rman script is
    #!/usr/bin/ksh
    export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
    export PATH=$PATH:/u01/app/oracle/product/10.2.0/db_1/bin
    /u01/app/oracle/product/10.2.0/db_1/bin/exp rman/cat@catdb file=/u02/rmanback/rm
    an_220108.dmp log=/u02/rmanback/rman_220108.log owner=rman statistics=none comp
    ress=n buffer=400000
    compress *.dmp
    exit
    2. I created a schedule as follows
    BEGIN
    DBMS_SCHEDULER.CREATE_SCHEDULE(
    schedule_name => 'rman_backup_schedule',
    start_date => SYSTIMESTAMP,
    end_date => '31-DEC-16 05.00.00 AM',
    repeat_interval => 'FREQ=DAILY; BYHOUR=4',
    comments => 'Every day at 4 am');
    END;
    3. I created ajob as follows.
    BEGIN
    DBMS_SCHEDULER.CREATE_JOB (
    job_name => 'rman_backup_job',
    program_name => 'rman_backup_prg',
    schedule_name => 'rman_backup_schedule',
    enabled=> true,
    auto_drop=> false
    END;
    While I am running the job I am getting the following error anybody help me.
    ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 2
    If I removed "compress *.dmp" line in rman script it is working fine.
    /* additional Info from dba_scheduler_job_run_details as follows */
    ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
    STANDARD_ERROR="
    Export: Release 10.2.0.3.0 - Production on Tue Jan 22 14:30:08 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Release 10.2.0.3.0 - Production
    Export"
    Regards,
    Kiran

  • Not able to deploy to register my mapping with OEM

    I am new to data ware housing.Iam using oracle9i warehouse builder.I created a source,target and mapping between these two using mapping editor.Then I have generated scripts bot not able to make OEM register.When I click the button "OEM register", it give 2 error messages.
    1. Specified Connection is not a valid Run time schema
    2. Please Make sure OEM Client installed locally or enter correct OMS domain domain in the configuration parameter.
    I know that some parameter should be set in preference dialog box but no idea how to set that.
    Can anyone help regarding this.
    Thanks

    created a project with following structure
    MyProject
    ----MySource (FlatFile)
    ----MyTarget
    Created a map between these 2 and named it "MyMapping".After successfully generating code for the map, "GenerationReults[succeed]" Dialog box opened.But Deploy and Run button are disabled so I tried clicking OEM Register button to get the following error message even after setting preference values.
    Please tell me how to make those buttons enabled.Is there another way.
    Error--
    Failed to register the jobs with OEM.: OEM Registration Failed. Please make sure you have OEM client installed locally, the Oracle Management Server is running, and you have entered correct connection information and OEM information under 'Preferences'.
    Incorrect domain entered or node not discovered. Please enter correct OMS domain name in the configuration parameter and make sure that the OMS is running.
    oracle.sysman.emSDK.client.omsClient.NoDomainException: singapore
    Job object failed to create, check to see if user has credentials.

  • Job RDDEXECL terminated with error.

    Hi!
    I am facing with hanging SPAM error in phase IMPORT_PROPER (patch of SAPKB70013 - SAPKB70016).
    The SPAM patch terminates after a few sec. in DDIC activation action.
    I have looked into log file and founded folllowing:
    The job RDDEXECL terminated with error.
    The reason seems to be sysntax error in program "CL_PROXY_SERVICE=======CP".
    Futhermore I could detect that table SI_WD_FIRST_MAIN_SCREEN cannot be activated.
    Can some one help me to solve this problem?
    Of great interest was the following:
    rescedule possibilities of job RDDEEXECL in order to contibue patch
    start of SPAM or tp-commando by ignoring this error
    Any helpful information will be very appreciated!
    Holger

    What do you mean with reimport?
    I tried for almost 100 times to restart the import.

  • Print job becomes massive with Flash Player 10.1 & 10.2?

    First off, some info.  This is rather old code, written in 2007/2008 with Flex 2 by someone no longer with the company.  It has worked just fine for years, but not anymore.  The application aggregates pricing data over several years, and shows it in a series of 5 or so charts depending on user options.  There is a print button which takes the charts, puts them into a print template, and prints the charts (using the FlexPrintJob function) - or at least that's what it should do.
    Here's the lowdown:
    Flash Player 10.0.x and lower (down to FP 9.x), it works beautifully.
    Flash Player 10.1.x with hardware acceleration off, it works beautifully.
    Flash Player 10.1.x with hardware acceleration on, it breaks.
    Flash Player 10.2.x under any condition, it breaks.
    Now, what I mean by 'breaks' is this: when printing, it spools a 600MB+ file to the printer, gets to ~500MB (roughly the print spool limit), and prints the template with the first chart complete and the rest of the charts missing anywhere from 1/2 to all of the chart area.  If a smaller dataset is used, the charts may or may not complete, but the print job is still massive - the lowest I've seen is 350MB.  In scenarios where it works beautifully, the print job is 12MB at most.
    This slice of the application is part of an application bundle we sell as a service to clients, and forcing a FP downgrade on them is not an option.
    Has anyone run into this issue, or know where I might start to fix it?  In leui of that, any suggestions for porting a Flex 2 application to a FB4 application?
    Thanks for your time, and any help.

    The only printing example I could find in the Flex 2 docs is the very simple one here - Flex 2 Developer's Guide > Flex Programming Topics > Printing > Using the FlexPrintJob class > Example: A simple print job
    Surprisingly, even with a basic print job, the issue appears - in FP 10.2, the print job is ~13MB, in FP 10.0, the print job is ~2.3MB.
    For reference, the code used for the example (from Adobe's docs) is as follows:
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
        <mx:Script>
            <![CDATA[
                import mx.printing.*;
                // Create a PrintJob instance.
                private function doPrint():void {
                    var printJob:FlexPrintJob = new FlexPrintJob();
                    // Start the print job.
                    if (printJob.start() != true) return;
                    // Add the object to print. Do not scale it.
                    printJob.addObject(myDataGrid, FlexPrintJobScaleType.NONE);
                    // Send the job to the printer.
                    printJob.send();
            ]]>
        </mx:Script>
        <mx:VBox id="myVBox">
            <mx:DataGrid id="myDataGrid" width="300">
                <mx:dataProvider>
                    <mx:Object Product="Flash" Code="1000"/>
                    <mx:Object Product="Flex" Code="2000"/>
                    <mx:Object Product="ColdFusion" Code="3000"/>
                    <mx:Object Product="JRun" Code="4000"/>
                </mx:dataProvider>
            </mx:DataGrid>
            <mx:Button id="myButton" label="Print" click="doPrint();"/>
        </mx:VBox>
    </mx:Application>

Maybe you are looking for