6 Replies Latest reply on May 8, 2014 1:38 PM by Lori Baysdon

    After migration from Solaris to Linux reports are not working correctly

    Lori Baysdon

      Oracle ebusiness 11.5.10.2 --seeded pdf reports

       

      Some are not running giving error:

      Emsg:Was Terminated By Signal 11

       

      Others run but are formatted incorrectly.

       

      Background:

      Migrated from solaris to linux. --11.2.0.4 database.  Solaris upgrade to dev 6i patchset 28 - everything works.

      On linux, had to install techstack then upgrade to dev 6i patchset28 also.


      I checked support and applied a patch that was a possible fix -

      Bugs: 5232832 - APPS6: BLANKS INSERTED INTO CHARACTER MODE OUTPUT

      later discovered it is just for bitmap report.


      Checked all the notes I found, but nothing seems to apply.


      My character set is the same on Solaris and Linux --  

       

      NLS_CHARACTERSET                              US7ASCII

      NLS_NCHAR_CHARACTERSET              AL16UTF16

       

      Anyone have any ideas? Thanks!

        • 1. Re: After migration from Solaris to Linux reports are not working correctly
          Hussein Sawwan-Oracle

          Is the issue with text reports? And is it with seeded ones (like "Active Users")?

           

          Do you have $ORA_NLS33 set?

           

          Thanks,

          Hussein

          • 2. Re: After migration from Solaris to Linux reports are not working correctly
            Lori Baysdon

            Active users works fine. I think the issue is pdf reports only seeded and custom...at least that is what the user tells me. ORA_NLS33 is not set.  Here are my nls settings:

             

            NLS_DATE_FORMAT=DD-MON-RR

            NLS_DATE_LANGUAGE=

            NLS_LANG=AMERICAN_AMERICA.US7ASCII

            NLS_NUMERIC_CHARACTERS=.,

            NLS_SORT=binary

             

            One thing that may or may not be a factor is this new system has mid tier and db tier on separate servers. The source is a single server for both.  The pdf output is from the database tier but shared via nfs mount.

             

            I am attaching 2 reports. 1 from source - PROD-Statement, 1 from new Linux system - Linux-statement.  This is one where formatting is off.

             

            In addition ARXSGPO.rdf  is one that fails with emsg:was terminated by signal 11.

            I can't find a way to attach a file, so here is what the linux report looks like, format is correct on the source system:


            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            iiiiiiiiiii DD-Mon-RR ttttttttttttt DD-Mon-RR rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr bbbbbbbbbb 9999999999.99- 9999999999.99-

            9999,999,999.99 999,999,999.99 999,999,999.99 999,999,999.99 999,999,999.99 9,999,999,999.99 USD 9,999,999,999.99

            bbbbbbbbbbbbbbb bbbbbbbbbbbbbb bbbbbbbbbbbbbb bbbbbbbbbbbbbb bbbbbbbbbbbbbb

            Page 1

            DD-Mon-RR 99999999999

            • 3. Re: After migration from Solaris to Linux reports are not working correctly
              EBSDBA

              Hi,

              Once we had same problem. After so many tries the developer copied the same program to a custom program and created a new template. All worked fine.

               

              Thanks

              • 4. Re: After migration from Solaris to Linux reports are not working correctly
                Lori Baysdon

                After looking around, it seems the problem may be the setup for noprint?  The drivers used by noprint for the source system are acrobat.  I tried changing the driver to --pasta universal so I can view pdf's still not working. I think what I am missing is:

                How do I set up noprint 'printer' ?  Any ideas?

                • 5. Re: After migration from Solaris to Linux reports are not working correctly
                  Lori Baysdon

                  posting new thread, this one is not going in the right direction.

                  • 6. Re: After migration from Solaris to Linux reports are not working correctly
                    Lori Baysdon

                    Signal 11 issue was resolved as follows:

                    The reports engine, on the upgraded Linux server, is not able to parse an sql validating with a table via dblink only at a specific place within the report. There are several other places within the report where it is able to parse the same sql, hence it is inconsistent and there are no pertinent error messages to that effect. The solution was applied by way of re-writing those validations to validate from within EBS itself and hence the functionality remains unaffected.


                    Formatting issue was resolved by re copying the rdf from the source in binary mode.  Something must have happened to the file with the original tarball, OR someone messed with the report on the target unkown to me!

                    Also I setup up pasta printing and drivers for the system and styles, so maybe it was a combination of the two actions.


                    Thanks everyone for your help.