Standby Database on a Source and target of different endian formats

Hi
I have a this well know case where the source server and target server are with different endian formats. I want to implement a Data guard 11g in this enviroment. How can I do to implementing having the issue of the different endian formats.
Thanks

Here is the answer.... for your learning....
Checking the Database Before Cross-Platform Database Conversion
As explained in "Basic Concepts of Cross-Platform Data Transportation", you can use the RMAN CONVERT DATABASE command to automate the copying of an entire database from one platform to another.
Before converting the database, see the list of CONVERT DATABASE command prerequisites described in Oracle Database Backup and Recovery Reference. Confirm that you meet all these prerequisites before attempting the procedure in this section.
One prerequisite is that both the source and destination platform must share the same endian format. For example, you can transport a database from Microsoft Windows to Linux for x86 (both little-endian), or from HP-UX to AIX (both big-endian), but not from HP-UX to Linux for x86 (big-endian to little-endian).
Note:
If you cannot use the CONVERT DATABASE command because the platforms do not share endian formats, then you can create a new database on a destination platform manually and transport needed tablespaces from the source database with cross-platform transportable tablespaces.

Similar Messages

Parametrized relation connections - don't work when source and target are different

Hi All,I have next problem:I am using parametrized relation connection firstConnection (user and (encripted)password are taken from parameter file). Here are values from param file: $DBConnection_source=firstConnection$DBConnection_source=firstConnection$ParamUser=svaba$ParamPwd=Dni32iRiH0Yjro1U04+RTC==  This is (source and target are same) working fine for years.
But now I need two different connection, i.e. source is (existing)   firstConnection and target is secondConnection. On both instances I have same user
  (svaba) with same password. I created second parameterized connection with user = $ParamUser    and password = $ParamPwd     Now, parameters are: $DBConnection_source=firstConnection$DBConnection_source=secondConnection$ParamUser=svaba$ParamPwd=Dni32iRiH0Yjro1U04+RTC== When run workflow, got error: ORA-01005: null password given: logon denied.I triede to change connections by entering values for password (not use parameters for password) got error: ORA-01017:invalid username/password:logon denied.When I am using same (parametrized) connection for source and target (any of these two) everything is fine. That is sign that connections are good. Does someone have any idea about this problem

Hi All,I have next problem:I am using parametrized relation connection firstConnection (user and (encripted)password are taken from parameter file). Here are values from param file: $DBConnection_source=firstConnection$DBConnection_source=firstConnection$ParamUser=svaba$ParamPwd=Dni32iRiH0Yjro1U04+RTC==  This is (source and target are same) working fine for years.
But now I need two different connection, i.e. source is (existing)   firstConnection and target is secondConnection. On both instances I have same user
  (svaba) with same password. I created second parameterized connection with user = $ParamUser    and password = $ParamPwd     Now, parameters are: $DBConnection_source=firstConnection$DBConnection_source=secondConnection$ParamUser=svaba$ParamPwd=Dni32iRiH0Yjro1U04+RTC== When run workflow, got error: ORA-01005: null password given: logon denied.I triede to change connections by entering values for password (not use parameters for password) got error: ORA-01017:invalid username/password:logon denied.When I am using same (parametrized) connection for source and target (any of these two) everything is fine. That is sign that connections are good. Does someone have any idea about this problem

One problem with constraints missing in source and target database....

DB Gurus,
In my database I am going to export and import data using datapump but dont specify CONTENT clause.
so when I start working on my application, I came to know there are some constraints are missing. now how to check what are the constraints are missing from Source database and how to create those missing constraints on Target database?
Suggest me if you have any idea.

Create a database link between source and target schema.
Use all_/dba_/_user_constraints to generate the difference using MINUS operator.
something like this:
select owner,constraint_name,constraint_type from dba_constraints@source
MINUS
select owner,constraint_name,constraint_type from dba_constraints

Issue in OWB mapping - when changing source and target database

Hi,
I need help for resolution of the issue I am facing when moving mapping from development environment to QA.
Here is situation,
We develop ETL using one source, one staging and one target database.
In development we use one control_center for Source to staging and another control center staging to target.
All works fine in development.
Now I have created new runtime repository and imported all OWB projects (with full dependencies, exact replica of development). Now I need to change source and staging and target as different database.
I have created new database location connections and defined/attached DB connectors with stage and target location.
Now issues are
1.     Two Staging mapping are not able to bound with source table (giving different error
a.     One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b.     Other mapping show error for source table/object not bound to repository
2.     All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
Not sure how to proceed from here.
I have recreated new repository and re-imported all project/mappings and defined all connection but still same issue.
Thanks in advance,
Vipin

1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
The above error were resolved when re-synchronized the table (for few I have to reimport the table) and mapping.
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
The above error still pending. My target mapping are not able to deployed/compiled.
For the above I have defined one Staging location to one target target location and target location have connector to staging (not sure if I have to define connector name same as staging location, as I have created DB connector with different name but reference database is same as staging location).
Mapping are assoicated with desired data locatoin and meta data.
control center is also have that data location.
Mapping are configured for the desired location.

OWB 10g -- Can't Create Database Links for Data Source and Target

We installed OWB 10g server components on a Unix box running Oracle 10g (R2) database. The Designer Repository is in one instance. The Runtime Repository and the Target are in another instance. The OWB client component was installed on Windows XP. We create a data source module and a target module in OWB. The data source is on another Unix box running Oracle 9i (R2) database. We try to create database links for data source module and target module, respective. But when we created and tested the DB links, the DB links were failed.
For the database link of data source, we got the following error message:
Testing...
Failed.
SQL Exception
Repository Error:SQL Exception..
Class Name: CacheMediator.
Method Name: getDDEntryFromDB.
Repository Error Message: ORA-12170: TNS:Connect timeout occurred
For the database link of target , we got the following error message:
Testing...
Failed.
API2215: Cannot create database link. Please contact Oracle Support with the stack trace and the details on how to reproduce it.
Repository Error:SQL Exception..
Class Name: oracle.wh.ui.integrator.common.RepositoryUtils.
Method Name: createDBLink(String, String, String, String).
Method Name: -1.
Repository Error Message: java.sql.SQLException: ORA-00933: SQL command not properly ended.
However, we could connect to the two databases (data source and target) using the OWBs utility SQL Plus.
Please help us to solve this problem. Thank you.

As I said prior the database link creation should work from within the OWB client (also in 10).
Regarding your issue when deploying, have you registered your target locations in the deployment manager and did you first deployed your target location's connector which points out to your source?
I myself had some problems with database link creations in the past and I can't remember exactly what they were but it had something to do with
- the use of abnormal characters in the database link name
- long domain name used in as names.default_domain in my sqlnet.ora file
What you can do is check the actual script created when deploying the database link so see if there's something strange and check if executing the created script manually works or not.

Single Code Page Unicode conversion when source and target are the same

Hi everyone. We have recently upgraded our non-unicode 4.7 to ECC6 non-unicode. Now we have begun researching the next step to convert to Unicode. I know we could have done the Combined Upgrade and Unicode Conversion but I wanted to do thorough testing after the upgrade to eliminate too many variables if problems arose.
So, my question is...has anyone done the Unicode conversion when source and target servers are the same? Most documentation I've seen recommends a system copy to another box first. I did find one forum thread that gave a high level approach to doing the conversion with just one server and listed this:
Step 1:- Run Tcode SPUMG to scan
Step 2:- Export Database
Step 3:- Drop Database
Step 4:- Create New Database
Step 5:- Import database
Step 6:- Chnage unicode Kernel
What are your thoughts? Is it supported? Am I wasting my time and should I just bite the bullet and buy yet another system? Thanks in advance.
-Anthony

Theoretically that's possible, yes. However...
> Step 5:- Import database
> Step 6:- Chnage unicode Kernel
the import must be done using the Unicode kernel.
So basically you can
- export the old systm
- uninstall system + database
- start as if you were installing "from scratch" on a new box
Markus

Is it possible to have source and target schema in the same DB instance ?

Hi All,
I'm using Oracle 11gR1.
I have switched source locations from other server to the one with OWB.
During deploy I get VLD-3064 and I can't deploy mapping because of many 'table or view does not exist' warnings.
Is it possible to have source and target schemas in the same instance ??
How to do it ?
Regards,
Martin

Hi Jörg,
Thanks for your help and quick answer.
I'd like to clarify a little your answer :
1. Are the any special privilages I need to set ? Currently I have only 'RESOURCE' and 'CONNECT' (I think I didn't have to add any other privs when that schema was located on other instance...)
2. Also VLD-3064 states that : 'Owning and referenced location of this connector are on the same database instance. Unless explicitly referenced in configuration settings no generated code will use the dataabase link resulting from deployment of this connector'. Does it mean I have to put something in configuration ?
Thanks,
Martin

Source and Target Table in the Same schema........will that work in ODI

Hi ,
Is it possible to have my source and target tables in the Same achema.......will it have any performance issues or some other issues in our ODI.......
I would like to know whether it works well or not .........
( To my understanding it wont have any issues ......But I am not 100 % sure on my judgement)
Thanks
AK

Yes, you're correct.
Just be sure about you load strategy, it means, if you need only to insert use the KM Control Append, but if need update too, try the IKM Oracle Incremental Update... I believe that will work better for millions of lines.
Anyway be sure that your database has the necessary tablespaces to manage huge data volume.

Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.

I am using VS 2012 and BizTalk 2013 and attempting to deploy an application to BizTalk when I get these errors:
Error 47
at Microsoft.BizTalk.Deployment.Assembly.BtsMap.Save()
at Microsoft.BizTalk.Deployment.Assembly.BtsArtifactCollection.Save()
at Microsoft.BizTalk.Deployment.Assembly.BtsAssembly.Save(String applicationName)
at Microsoft.BizTalk.Deployment.BizTalkAssembly.PrivateDeploy(String server, String database, String assemblyPathname, String applicationName)
at Microsoft.BizTalk.Deployment.BizTalkAssembly.Deploy(Boolean redeploy, String server, String database, String assemblyPathname, String group, String applicationName, ApplicationLog log)
0 0
Error 49
Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to deploy map "XXX.BTS2013.XXX.Maps.map_XXXX_R01_InsLabProc".
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present. Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
0 0
Error 46
Failed to deploy map "XXX.BTS2013.XXX.Maps.map_XXXX_R01_InsLabProc".
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
0 0
I also tried to Import a MSI file from our test environment to see if that would work...got the same errors. After spending hours (not kidding) looking for an answer, all I could find is that a hotfix would work. So, I got the hotfix from Microsoft
Support and applied it then rebooted. Still getting the same errors. I'm absolutely at a stand still. Interesting that I got this application to deploy yesterday and then the next time I deployed it I started getting these errors. I'm
ready to pull my hair out!
Is there an answer for this out there somewhere? Any help would be appreciated.
Thanks,
Dave

Hi Dave,
Which hotfix have you applied? I don't think a hotfix of this issue is available for BizTalk 2013 yet. You should create a
support ticket with Microsoft to get a solution.
If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Keeping table name same in source and target

is it possible to keep the table name the same in source and target (they're on sepearte databases). Seems like OWB wants to rename the output table (usually adds 1 on the end). When I tried to rename I got a message saying that table name exists.

In my mapping.
First I defined a source and a target. The table on the target doesn't exist yet.
I open mapping editor...drag the table from my source. Let's call it TABLE_A. Then I add Table operator to the mapping (choose create unbound operator with no attributes option). For the name I choose TABLE_A...however when I click OK it then changes the name to TABLE_A_1.
So I double click on the table and change the name to TABLE_A and then I get the message that the table already exists.

Connecting the source and target schemas to ODI

Hi ,
I have recently started learning ODI tool for data integration. I need to use this tool as a part of Deal Management product related work.
I have gone thru the documentation available in OTN for ODI. they were describing everything using the demo environment.
problem:
Can any one please tell me how to connect source schema and target schema to the ODI ...?
Both the source and target schema are in the Oracle database of the loaclhost.

Hi,
Right Click ur Dataserver , In the bottom u will have option insert physical schema.
Click that u will have window opened........
In the Definition Tab:
Specify ur Schema name and Work schema .......u r going to use .
Enable the default option also....
In Context Tab:
Specify ur context Name and Type in the Name u want to have for ur logical Schema, it autmatically creates the logical schema ...for u.
and click ok .
hope it helps u.....
Thanks
AK

The source and target structure have a different number of fields

Hi,
I am new to workflow and I am trying to create an attachment in Workflow (SAP ECC 6.0) and pass it through to a User Decision (User Decision works fine) however the workflow is failing on the attachment step with u2018The source and target structure have a different number of fieldsu2019. The bindings check ok. Please see details below.
I have used document u2018Creating Attachments to Work Items or to User Decisions in Workflowsu2019 by Ramakanth Reddy for guidance. Thanks in advance.
1) Workflow containers (SWDD)
WORKITEMID (import)
ZSWR_ATT_ID (export)
SOFM (export)
2) Task Container (PFTC)
1 Import parameter defined u2013 WORKITEMID (swr_struct-workitemid)
2 Export parameters defined
- SOFM (Ref. obj. type SOFM)
- ZSWR_ATT_ID (swr_att_id-doc_id)
Binding task -> Method
Binding for 1 parameter (import) defined
Task <- Method
Binding for 2 parameters (export) defined
3) Z BOR object created with a Method, Method Parameters and Event (SWO1)
1 import parameter defined
2 export parameters defined
Method calls FM SSF_FUNCTION_MODULE_NAME, CONVERT_OTF, SCMS_XSTRING_TO_BINARY and SAP_WAPI_ATTACHMENT_ADD
Workflow is triggered by FM SAP_WAPI_CREATE_EVENT, Return_code = 0
Event_id = 00000000000000000001
Test results
A) Triggered by ABAP/ FM SAP_WAPI_CREATE_EVENT - SWI2_DIAG results
Work item 14791: object <z bor object name> method <method name> cannot be executed. The source and target structure have a different number of fields (this message is repeated 3 times). Error handling for work item 14791. No errors occurred -> details in long text (message is repeated 3 times).
Message no. WL821, OL383, WL050 in long text
B) Z BOR Test method <execute>
Enter workitem id.
Runtime error - Data objects in Unicode programs cannot be converted. The statement "MOVE src TO dst" requires that the operands "dst" and "src" are convertible. Since this statement is in a Unicode program, the special conversion rules for Unicode programs apply.
In this case, these rules were violated.
Program                             SAPLSWCD
Include                                LSWCDF00
Row                                    475
Module type                        (FORM)
Module Name                      MOVE_CONTAINER_TO_VALUE
C) Z BOR Test method <debugging>
Enter workitem id.
SAP_WAPI_ATTACHMENT_ADD, return_code = 0, message_lines = Attachment created
both swc_set_element container work ok
Runtime error occurs after end_method executed. Data objects in Unicode programs cannot be converted.
D) Workflow test
Enter workitem id <execute>
Task started> Workflow log> Status = Error
Workflow errors in Attachment step (however Office document can be viewed in details for step).

Problem has now been resolved. Problem was related to use of swr_att_id structure and swc_set_element statement in BOR program - problem resolved by only setting w/f container to swr_att_id-doc_id.

Issue in mapping the same source and target fields

Hi All,
I am working on PI 7.0 and currently I am connecting to PI 7.0 via citrix desktop . Problem here is : in the mapping , direct mapping option that is available to map the same source and target fields is disabled . I do know that this is due to some java version issue .
What I want to know is there any possibilty of solving this issue without installing an updated java version ?
Regards
Vinay P.

I've faced the same for many times and all of that were due to Java version.
1st of all, you have to check the authorizations you have. If you have enough (DEVELOPER_J2EE, CONTENT_ORGANIZER_J2EE, and so), and - obvious but very often forgotten - you have to assure you're trying to change it in the message mapping change mode On.
Then, last shot should be downgrade your Java version.
The 1.4.2 JRE version allow you to use not only the Mapp the Identical field but also Dependencies, Clear Mapping and some other tools/buttons. As mentioned above, if there's a fix in the new Java releases, I do not know (hope so) and would appreciate if you could let us know.
Tks.

HOWTO set source and target in WTK KToolbar

I am having trouble getting my MIDlet compiled when pressing the Build button in the WTK's KToolbar. I get the following error:
generics are not supported in -source 1.3
This is because I have JDK 1.6 installed and I'm trying to use a Vector in my code that is typed.
How do I configure the javac settings through the KToolbar so it uses the javac -source and -target arguments?
Thanks.

The thing is like
while practicing in my institute I had used "//ECCserver/SAPMNT" as path for both sender and reciever communication channels...
now i'm unable to write the path for both
please help me out

Master Data ------ Source and Target Mapping

I want to know the source and target mapping of some master data elements like plant,vendor,customer,workcenter.
Where can I get it. Please provide the relevant documents or links.

Hi,
Check in RSOSFIELDMAP table.
Thanks
Reddy

Standby Database on a Source and target of different endian formats

Similar Messages

Maybe you are looking for