• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 98
  • Last Modified:

manager

We are using a 3.0 version of Reportsmith to access data in our ERP system. Our ERP is upgrading and going from Oracle 11 database to oracle 12. We are upgrading our Oracle Client on the pc from Oracle 11 to Oracle 12 as well. problem we have now encountered is that Oracle 12 client and Reportsmith 3.0 do not play well together. has anyone run into this issue and found a way around some of the problems...like RTrim and trying to concatenate 3 fields together (like first, middle, last name) into 1 field? R/S also doesn't like derived fields now that we are using oracle client 12. any help is greatly appreciated.
0
Julia T
Asked:
Julia T
  • 2
2 Solutions
 
Mark GeerlingsDatabase AdministratorCommented:
I've never used or seen Reportsmith, but one approach you could consider that may help would be to create views in the Oracle12 database that do any trimming or concatenating or other formatting that you need, then any reports you need in Reportsmith can simply select the columns as the views present them.

Another advantage of this approach is:  if any of your reports need to join data from two or more tables (most reports from most ERP systems need to do this) the performance advantage of doing these joins in database views instead of in a reporting engine can be *VERY* significant.  This varies of course among reporting tools, ERP systems, and the particulars of your reports.
0
 
Geert GruwezOracle dbaCommented:
use oracle  11 client again.
you can leave the database on oracle 12.

when upgrading, the oracle database is upgraded first and tested with the original clients
upgrading oracle clients is a separate step

some vendors actually check the version of the oracle client
and some go even further in issueing compatibilty warnings

reportsmith will not be using oracle 12 features, unless you upgrade that too to a version which does
using oracle 11 client on an oracle 12 database is fine in this case
0
 
Geert GruwezOracle dbaCommented:
you don't have to take my word for it ...
take oracle's :http://docs.oracle.com/database/121/UPGRD/app.htm#UPGRD12541

they state: the oracle database has to be an equal or higher version than the oracle client version

this setup matches that description:
oracle database = 12
oracle client = 11

it usually starts to get a problem when the client is 3 major releases different from the database release
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now