Related to export/backup planning schema before Planning app. migration

Hi,
I need to take backup of Planning planning schema before Planning application migration- (from 9.3.1 to 9.3.1)
1) does all Hyperion services need to be running? for cssexportimport and schema backup?
2) does it mean to export/import of schema which we have associated with datasource/particular application?
3) if we copy SID from target before schema restore and then we store SID after schema restore will it be always successful (as i don't know from where i can check the owner of application from source server).
4) Should we stop planning services before schema restore?

Kumar 1 wrote:
Hi,
I need to take backup of Planning planning schema before Planning application migration- (from 9.3.1 to 9.3.1)
1) does all Hyperion services need to be running? for cssexportimport and schema backup?You need Shared services running for CSSExportImport, for the schema that just needs the Oracle database running
2) does it mean to export/import of schema which we have associated with datasource/particular application?You will have already created the datasource on your target.
3) if we copy SID from target before schema restore and then we store SID after schema restore will it be always successful (as i don't know from where i can check the owner of application from source server).The user should be the same application owner otherwise you will experience issues with the SID
4) Should we stop planning services before schema restore?You should really stop planning, then restore the schema, then start planning
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Error relating a company code to a valuation plan

Hello,
I am trying to relate my company code to a valuation plan in OAOB transaction but it appears the error AC551. I have checked it and I don´t know where could I enter the value for VAT indicator for nontaxable transactions.
Could you help me with this issue?
Thanks a lot!

Hello
The result of the check of company code shows that important global
parameters from Financial Accounting are missing for Asset Accounting.
One or more of the following fields are affected:
Currency
Chart of accounts
Fiscal year version
Input tax indicator for non-taxable transactions
You cannot use the company code for Asset Accounting without this information.
Please check input tax code for non-tax relevant postings
(for example depreciations) can no longer be maintained via
IMG -> Fin. Accounting -> Asset Accounting
Maintenance is done via the IMG using the following path:
Financial Accounting -> Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Posting -> Allocate tax codes for non-taxable
transactions or transaction OBCL. Note 47055 is for your reference.
regards
Ray

Planned order is creating before planning bucket for a specific material.

Planned order is creating before planning bucket for a specific material.
Eg: Planning Bucket future: 12 months & Start date- 01/02/2012, but Planned order Availability/Requirement date is 12/23/2011.
What causes this, how to fix it? Please suggest u2026
Thanks
Ravi

Since your planning bucket start date is in the future, so this is normal that the system is trying to satisfy the demand in jan2012 bucket by creating a receipt on Dec23, 2011.
Reasons for RECEIPT to be generated earlier is
(1) There might be a FIRM HORIZON( SNP PROD HOR)
OR
(2) There might be a GR time and the system is considering that time
In Customizing for Advanced Planning and Optimization -> Supply Chain Planning -> Supply Network Planning (SNP) -> Basic Settings -> Maintain Global SNP Settings, in the SNP:GR for Plnd Ords field, you have selected Processing Time.
Blank out these times and see if it works, else do one of the following:
(1) Set Period Factor(LOT SIZE TAB of PRODUCT MASTER) to 1, so that the receipts get created at the end of the bucket.
OR
(2) Create your demand at the end of the planning bucket period
Thanks
Kumar

Warning Message Should come if actual delevery date is before planned date

Dear all;
is there any settings to set
Warning Message if actual delevery date is before planned delevery date mentioned in the PO?
Thanking You;
Regards;
Joydeep Mukherjee

Hi,
Goto the below path,
SPRO->Materials MAnagement->Purchasing->Environment Data->Define Attributes of System Messages
Click on new entries & maintain your relevant message & mark it as 'W' in the category.
Regards,
Divya

Migration of Planning Schema (Oracle DB)

When migrtating the underlying planning schema from one environment to another, wont it bring all metadata and the webforms from the old to the new environment?

here are the steps followed:
1) new schema (ABC) created in target database
2)DSN created
3)Blank app called ABC is created in the schema ABC
4)XYZ ( the source schema) is copied over ABC ( the new schema)
Does planning need a bouncing of services? i am not sure if they performed it.

I'm a student, i have join the student plan already,but on that before i purchased the photoshop plan, now i would like to cancel the photoshop plan because the plan is duplicate and i have to pay more the monthly fee.

i'm a student, i have join the student plan already,but on that before i purchased the photoshop plan, now i would like to cancel the photoshop plan because the plan is duplicate and i have to pay more the monthly fee.

Cancel your membership or subscription | Creative Cloud
https://helpx.adobe.com/x-productkb/policy-pricing/cancel-membership-subscription.html
If you need help from Adobe support try chat:
For the link below click the Still Need Help? option in the blue area at the bottom and choose the chat option...
Creative Cloud support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html ( http://adobe.ly/19llvMN )

JAVA error when exporting to reporting schema ODDM 4.1

When attempting to export a design to a reporting schema, we received the following error:
ERROR ReportsHandler - error exporting to reporting schema:
java.lang.classcastException: oracle.dbtools.crest.model.design.relational.column cannot be cast to oracle.dbtools.crest.model..design..relational.columnView
at oracle.dbtools.crest.exports.reports.RSViewColumn.export (RSViewColumns.java:43
at oracle.dbtools.crest.exports.reports.RSRelationalModel.export (RSRelationalModel.java:62)
at oracle.dbtools.crest.exports.reports.ReportsHandler.export (ReportsHandler.java:135)
at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run (ControllerApplication.java:2079)
We downloaded and installed ODDM 4.1 (EA-1) build 4.1.0.866 to resolve an issue with column widths when exporting to the reporting schema (per SR 3-10154440761). This is the 64 bit version with the included JAVA 1.8 JRE.

David,
We migrated this model from data modeler 3.3. That Model was created from an import from Oracle Designer. We have not yet tried to import the data model from Oracle Designer directly into v4.1 but are planning to do so shortly. When we tried to export that design (from v3.3) to the reporting schema, it failed with object too large for column errors. We wrote SR 3-10154440761 and were advised by Michael Wickham to use v4.1 EA as the column size issue had been resolved in this version. It was apparent that the export to the reporting schema was making more progress before it failed on the JAVA error.
We are trying to migrate from Oracle designer to Oracle Data Modeler

Exporting/Importing partition schema

Hi,
We are trying to manage multiple repositories for a project and in
particular we use a devopment/test rep and a production rep ( containing a
production plans snapshot ).
When a plan is moved from a development repository to the production one,
the partitioning previously done is lost. In this case developers have to
partition from scratch.
Moreover in our repository management policy ( apart clean up ) , we
destroy periodically development repository and import saved plans in a new
created one. This procedure causes the same problem described before.
Is there any chance to export the partition schema done in development
repository in order to re-apply the partitioning to the same plan in new
one, using fscript ?
Is there any other way to do it ( maybe via repository hooks and a tool
application ) ?
Thanx
Fab

Fabrizio,
We have a tool that will do this, and a number of other things for you. It
not only saves partitioning information, but it also:
* Reads your application defintion, along with the partitioning information
from the repository,
* Creates deployment and installation scripts,
* Analyzes your application for over 20 different performance and
scalability problems,
* Captures the supplier plan relationships for each partition as well as
for the entire application,
* Graphically shows partitioning structure, similar to partition workshop,
along with all partition and service object properties,
* Has Web and IIOP property sheets which are read from the application,
* Saves operational information, such as outage schedules and external
interfaces,
* Records special runtime properties of classes in your system
We offer this as part of our "Designing for Deployment" workshop. You can
send me a separate message for information about the workshop and the tool.
Don
At 06:35 PM 4/10/98 +0200, Fabrizio Barbero wrote:
Hi,
We are trying to manage multiple repositories for a project and in
particular we use a devopment/test rep and a production rep ( containing a
production plans snapshot ).
When a plan is moved from a development repository to the production one,
the partitioning previously done is lost. In this case developers have to
partition from scratch.
Moreover in our repository management policy ( apart clean up ) , we
destroy periodically development repository and import saved plans in a new
created one. This procedure causes the same problem described before.
Is there any chance to export the partition schema done in development
repository in order to re-apply the partitioning to the same plan in new
one, using fscript ?
Is there any other way to do it ( maybe via repository hooks and a tool
application ) ?
Thanx
Fab
============================================
Don Nelson
Regional Consulting Manager - Rocky Mountain Region
Forte Software, Inc.
Denver, CO
Phone: 303-265-7709
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"Until you learn to stalk and overrun, you can't devour anyone" - Hobbes

Export / Backup all the production data

Dear Experts,
Thanks for your attention!
Due to we have some upgrading issue in our production system. We plan to re-install the GRC AC SP10 in PRD.
We have go-live for half a year, there are around 500 requests in PRD, all these transaction data need to be export / backup before re-installation.
Could any one give us any advice?
Thanks a lot!

Hi,
This will be handled by BASIS team, you need not worry. Once the data was restored you need to amke sure all the production data was avilable with configuration settings, audit trial, all the requests data.
If this was first time you are performing, better check out restore on non-production server and identify any issues and resolve and then proceed onto production.
Backup and restore will be done only by basis and documents avilable in market place, also that was dependent on your DB type.
regards.

How to ZIP Oracle Datapump export backup file

Hello All,
My customer is asking to give him the production data dump to the following path \\138.90.17.56\OMNISAFE.
I really don't understand his requirement and he also wants me to zip the export backup file. How do I do that, Do you know any unix command to zip backup files.
thanks and regards
cherry

1013498 wrote:
Well Thanks for your reply.....my oracle version is 11.2.0.3.b and if we have the compression option can you please elaborate how to do that......
It's in the documentation. See Data Pump Export
let us say my expdp file is abc.dmp...should I give the command gzip abc.dmp or any different.
Let me google that for you
One more question what does teh customer mean by production data dump to the following path \\138.90.17.56\OMNISAFE. please explain
How do we know what the customer means? Why don't you ask him?
That said, it looks like a url to an ip address and a defined folder at that ip address. Again, if the customer wants you to send them a file, you need to be working with said customer on the mechanics of accessing their system.
All that said ....
Learning how to look things up in the documentation is time well spent investing in your career. To that end, you should drop everything else you are doing and do the following:
Go to tahiti.oracle.com.
Locate the link for your Oracle product and version, and click on it.
You are now at the entire documentation set for your selected Oracle product and version.
BOOKMARK THAT LOCATION
Spend a few minutes just getting familiar with what is available here. Take special note of the "books" and "search" tabs. Under the "books" tab (for 10.x) or the "Master Book List" link (for 11.x) you will find the complete documentation library.
Spend a few minutes just getting familiar with what kind of documentation is available there by simply browsing the titles under the "Books" tab.
Open the Reference Manual and spend a few minutes looking through the table of contents to get familiar with what kind of information is available there.
Do the same with the SQL Reference Manual.
Do the same with the Utilities manual.
You don't have to read the above in depth. They are reference manuals. Just get familiar with what is there to be referenced. Ninety percent of the questions asked on this forum can be answered in less than 5 minutes by simply searching one of the above manuals.
Then set yourself a plan to dig deeper.
- *Read a chapter a day from the Concepts Manual*.
- Take a look in your alert log. One of the first things listed at startup is the initialization parms with non-default values. Read up on each one of them (listed in your alert log) in the Reference Manual.
- Take a look at your listener.ora, tnsnames.ora, and sqlnet.ora files. Go to the Network Administrators manual and read up on everything you see in those files.
- *When you have finished reading the Concepts Manual, do it again*.
Give a man a fish and he eats for a day. Teach a man to fish and he eats for a lifetime.

Difference between Pension plans and savings plans

Dear Friends,
I'm familiar with the configuration of savings plans. But I have no idea about the pension plans. I realize that some of the basic steps are common to both savings and pension plans but what is the main difference from a config perspective?.
If any one can kindly explain the necessary steps to set up pension plans or if there is any document which talks about it please please let me know.
I appreciate the help and thanks in advance.

IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
Define Cost Variants:
In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Option
u2022 Dependent coverage
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
Health Plan Attributes:
In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
You assign to each health plan:
u2022 Its options
u2022 Relevant dependent coverages
u2022 The cost variants for the combination of options and dependent coverages
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
Insurance Plans:
In this step, you define general data for insurance plans
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
Coverage Variants:
In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual coverage in this step. You simply define how coverage varies according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define coverage variants, you need to do the following:
1. Determine how often coverage varies for different coverage options.
This indicates how many coverage variants you need. Note the following:
u2022 If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
u2022 If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
u2022 If a plan has options, you will need a coverage variant for each option.
2. Determine how coverage varies according to employee data.
This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
Coverage Rules:
In this step, you define the actual coverages for a plan.
You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
Coverage can be defined as a flat amount or as a factor of salary
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
Cost Variants:
In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often cost varies for different coverage options:
u2022 If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
u2022 If you have set flat coverage options and the flat costs are directly
proportional to the coverage stated in the flat cost, you need only one
cost variant.
u2022 If an employee can choose any amount of coverage within a range and the
cost of the coverage is directly proportional to the coverage, you need
only one cost variant.
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
Insurance Plan Attributes:
In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
You define the insurance plan options, then associate to each insurance plan:
u2022 Cost variant
u2022 Coverage variant
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
Combined Coverage Limits:
When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
In this chapter, you define these combined limits as follows:
1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
3. The second view defines the other side of the equation in terms of the plan coverages
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
Combined Coverage Limit Expressions:
In this step, you enter the second half of the equation, as discussed in combined coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
Imputed Income for Selected Benefits:
In this section of the IMG, you define the criteria needed to calculate Imputed Income.
Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
Review Calculation Factors for Imputed Income:
In this step, you check that the Imputed Income Rate Table entries are correct.
The imputed income age groups are associated with the rates/factors set by the IRS
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
Savings Plans:
In this step, you define general data for savings plans.
You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
Employee Contribution Variants:
In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contributions in this step. You simply define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
Employee Contribution Rules:
In this step, you define the employee contribution limits for each plan.
You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define minimum and maximum employee contribution in the following ways:
u2022 As a fixed amount
u2022 As a percentage of salary
u2022 As a contribution unit
In Payroll, the total employee contribution is the sum of these amounts
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
Employer Contribution Variants:
In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contribution in this step. You only define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
Employer Contribution Rules:
In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define the employer contribution and the contribution limit in either of the following ways:
u2022 As a fixed amount / as an amount per unit contributed by the employee
u2022 As a percentage of employee base salary or employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
Assign Savings Plan Attributes:
In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
u2022 EE contribution variant
u2022 ER contribution variant

I have several very important school related documents on my iPad in the Pages app. Ever since i updated to iOS5, i can no longer open any documents in Pages that I made before I updated. Please help

I have several very important school related documents on my iPad in the Pages app. Ever since i updated to iOS5, i can no longer open any documents in Pages that I made before I updated. Please help

Without the iPad connected, open up iTunes on your computer. Go to iTunes/Preferences/Devices and delete the backups that you're absolutely certain do not have the documents. Refer to figure below.
iTunes, select the iPad and then select the Summary tab. Follow directions for Restore and be sure to say "NO" to creating a backup. (You don't want to create a new backup that does not have the docs.) You will then be warned that all data (apps, music, movies, etc.) will be erased but, as the Restore finishes, you will be asked if you wish the contents of the backup to be copied to the iPad. This time, say "yes."
Repeat all of the above as required until you get the docs.

Unable to remove Workforce Planning formulae in Planning 9.3.1.1.16

Hi All,
We are on using Planning 9.3.1.1.16 and are unable to remove member formulae from Planning.
Our Planning application is EPMA (9.3.1.3) enabled. When refreshing the Planning application we receive the following error:
Error [1200497] detected in member formula for member "Regular Headcount".
Error [1200497] detected in member formula for member "Departed Headcount".
Error [1200497] detected in member formula for member "LOA Headcount".
Error [1200497] detected in member formula for member "Maternity Headcount".
Error [1200497] detected in member formula for member "On Sabbatical Headcount".
Error [1200497] detected in member formula for member "Contractor Headcount".
Error [1200497] detected in member formula for member "Temporary Headcount".
Error [1200497] detected in member formula for member "Other Headcount".
Error [1200497] detected in member formula for member "Turnover Headcount Adjustment".
Error [1200497] detected in member formula for member "Regular FTE".
Error [1200497] detected in member formula for member "Contractor FTE".
Error [1200497] detected in member formula for member "Temporary FTE".
Error [1200497] detected in member formula for member "Other FTE".
Error [1200497] detected in member formula for member "Turnover Adjustment".
STEPS TO REPRODUCE :
-In EPMA Master Library, remove the formulae for the above members and save the changes every time
- In Planning remove the member formulae for the above members (EDIT_DIM_ENABLED set to TRUE). This step may not be required however I tested it and was able to reproduce the issue
- Deploy the EPMA applicatoin. Deployment is successful
- Refresh Planning app. Refresh is successful
- Now change any property for any of the above members in EPMA. For example add an alias of Turnover Adj to the "Turnover Adjustment" member and save.
- Deploy the EPMA app => Successful
- Refresh Planning app=> Fails with same above error
Observation: The member formulae are back in Planning not EPMA. It looks like edit workforce members somehow causes the formulae to reappear in Planning.
Has anyone come across this issue?
Thanks for your help.
Seb

Just in case anyone has a similar issue...
Thsi was reported as bug #7411035 (ie: Character Limit for Member Formulas ). Details from Oracle Dev below:
The character limit was 2000 causing longer member formulas to fail during an application deployment. An underlying bug was found during investigation of the member formula limit and we think this is the cause of your particular issue. The problem was with empty member formula string. During the deployment process there are EAS side checks. EAS will only accept a member formula if it contains at least one character(length > 0), else the formula
field is rejected in the deployment XML file.
The script below copy the member formula to a different table and then delete the original. So it is quite a destructive query to run.
Prior to executing the query, a full EPMA/Planning applications backup should be performed (including essbase side) and the EPMA Dimension Server services (particularly the Process Manager) should be stopped.
######### SQL SCRIPT #########
insert into DS_Property_Member_Memo
select i_library_id, i_dimension_id, i_application_id, i_member_id, i_property_id, c_property_value as x_property_value
from ds_property_member pm
where pm.i_property_id = (select i_property_id from ds_property
where c_property_name = 'MemberFormula')
and not exists (select * from ds_property_member_memo pmm
where pmm.i_library_id = pm.i_library_id and pmm.i_dimension_id = pm.i_dimension_id
and pmm.i_application_id = pm.i_application_id and pmm.i_member_id = pm.i_member_id
and pmm.i_property_id = pm.i_property_id)
delete from ds_property_member
where i_property_id = (select i_property_id from ds_property where c_property_name = 'MemberFormula')
######### END OF SCRIPT #########
Seb

EXPORT/IMPORT SBO SCHEMA ERROR

Hello,
We have a client who is working with SAP BusinessOne version for HANA, with HANA PLATFORM rev. 69 and I need to export your database and import it to our development server .
To backup/restore the database I have performed the following steps :
1 - I have made the export of a ' SCHEMA ' with "EXPORT "SBOXXX_ES"."*" AS BINARY INTO '/tmp/SBOXXX_ES' WITH REPLACE THREADS 10;".
2 - I have compressed files in Linux using the command : tar- czvf .....
3 - I've Unzipped the files to our local server.
4 - Performing the ' IMPORT ' command gives me the following errors,I tried two ways to import :
4.1 - IMPORT "SBOGXXX_ES"."*" as binary from '/tmp/SBOXXX_ES' with replace threads 10 rename schema "SBOXXX_ES" to "SBOXXX_ES_2";
Error mesage: SAP DBTech JDBC: [2]: general error: [Other schema]._SYS_SS_CE_1957622_RET not found in the import directory.
4.2 - IMPORT "SBOXXX_ES"."*" as binary from '/tmp/SBOXXX_ES'
with replace threads 10 NO DEPENDENCIES
rename schema "SBOXXX_ES" to "SBOXXX_ES_2";
Error mesage: SAP DBTech JDBC: [2048]: column store error: table import failed: [30111] Binary import failed (could not execute create statement);invalid column view: ODLN: line 7 col 45 (at pos 506) at ptime/query/checker/check_cube.cc:259
I guess when you export the " SCHEMA " exported la la " DEPENDENCIES ON" option and these are generating the first error when importing .
If the error is of the DEPENDENCIES, in which DEPENDENCIES are stored files to edit , and remove all that is giving the error (SYS_SS_CE_1957622_RET ) .
Thank you very much for your support .
Adria.

Hi Adria,
I asked you to test the import on the system you exported from to determine if the problem is occurring because you are transporting the files from system 1 to system 2. If it works on point of origin we should investigate why the transfer is corrupting the file. I thought it would be ok because you are renaming the schema as part of the process. I would not want to import @point of origin without the rename.
Whenever some one asks me how to export a schema and import it with a different name I provide:
export "SBODEMOGB"."*" as
binary into '/home/SBODEMOGB' with replace threads 10;
import "SBODEMOGB "."*" as
binary from '/home/SBODEMOGB_901' with replace threads 10 rename schema "SBODEMOGB" to
"SBODEMOGB_NEW";
You are using the statement I would provide.
I cannot find an hints for the error reported (SYS_SS_CE_1957622_RET). If you do not see anything more helpful in the trace file I would suggest opening a customer message.
Best regards,
Duncan

Daily export backup

Hi,
I have production & DR database of 350gb version 10.2.0.4 on aix 5.3 platform.
In morning time after completion of daily batch, we are taking export backup (by stopping application services till application is not available for users) by using datapump utility which is taking 2 to 2.30 hrs to completes.
After that we have starting the application services and then only application available for users.
This export backup dump we are daily using for restoration on another development server.
Kindly help me, is there any option to avoid export backup time so that it will not affect buisness time.
and also i can do daily restoration on development server.
Please help.
Regards,

In morning time after completion of daily batch, we are taking export backup (by stopping application services till application is not available for users) by using datapump utility which is taking 2 to 2.30 hrs to completes.
After that we have starting the application services and then only application available for users.
This export backup dump we are daily using for restoration on another development server.
Kindly help me, is there any option to avoid export backup time so that it will not affect buisness time.
and also i can do daily restoration on development server.if you want complete database refresh?
you can use STREAMS.
If certain schema/objects you can use MViews.

Related to export/backup planning schema before Planning app. migration

Similar Messages

Maybe you are looking for