DSXchange

Interesting. An exact search for "APT_PMwaitForPlayersToStart failed" here returned 21 other matches, did any of them help?

I'm not sure how well supported that would be, seeing as how BOOLEAN is specific to PL/SQL rather than being a data type allowed in table columns. I'm guessing you may end up having to change the procedure to use a more 'traditional' data type for that parameter. In your shoes I'd also open a case w...

Which is what was being suggested - trim the resulting string as shown.

Depends, maybe yes maybe no. Usually one would try both ways to check.

What is the actual characterset, the $NLS_LANG setting for your target database? I know you've stated what you set the stage in the job to, how about the database itself?

Kim's stuff is here btw.

You need something to feed a single record to the SP stage with those two values as columns that can be bound into the call. In PX, a Row Generator should work, perhaps with an intermediate Transformer to slide the values into the link that you need.

I think you are *basically* correct about the "false errors", you'll get that message from the data viewer whenever it runs out of records to display... it's just that you run out of them right away when whatever you are viewing is empty. :wink: The load/sqlldr issue is a whole 'nuther ket...

4. "steps to take to load fact table". This part is actually the easiest part. Stream your core data in - which is typically whatever measures the fact contains and the associated business keys - do lookups against all of the fact's dimension tables to retrieve their surrogates and then in...

Hmmm... how are they delivered? As a zip file? Perhaps if so they should just be unzipped into the proper location, whatever that might be.

Do an exact search here for "OMD.XML.DIR" and see if any of the other posts on the topic help.

You need a smarter script. As you've found, sqlplus only reports back an error if the session itself has issues running but could care less what happens with the sql itself that you run inside it. Capture the output of the session to a file and then grep through it afterwards for ORA (etc) errors. I...

You mean multiple bytes per character. And I assume you are using byte semantics in your database? Meaning your target is VARCHAR2(3000) BYTE rather than VARCHAR2(3000) CHAR, yes?

Nope, the limit is 4K. And (allegedly) that error should only occur for "LONG" data types.

http://ora-01461.ora-code.com/

I'm curious, what version of Oracle are you running?