Question

Not able to see the generated DDL/Schema file from BIX Extract in the output directory

We are implementing BIX in our organization to extract some properties in CSV to our application server. We specified the path and tested the connectivity. It is good. When we run the extract, it is showing a success message and few records are extracted as well,  but we are not able to see the extracted sql/manifest file in the local directory. I appreciate your help.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
March 4, 2016 - 9:52am

Yes, Actually we were trying with DB schema. So, Generated DDL for that purpose. The issue is resolved now.

The reason for that issue is we were trying to extract the records from the Framework layer rather than the Implementation layer. Thanks for your help Celeste and Rajiv.

Comments

Keep up to date on this post and subscribe to comments

March 3, 2016 - 12:07pm

I'm a little confused about what output format you are using.  Are you extracting to CSV or DB?  If you are extracting to CSV then the extracted file will be on the app server in the directory specified if running from the UI or if running from the command line it will be on the node you are running from.  For a DB extract then obviously the output would be in the target DB.  If you are generating the DDL then again will depend on if you are running from UI or command line on what node it will be on.  If you post the PegaBIX log file the details should all be in there.

March 3, 2016 - 12:31pm
Response to CelesteDufresne_GCS

Thanks Celeste Dufresne for the reply.

I am extracting to CSV and not able to find it on the app server. Then I tried with DDL generation, even I didn't find the sql file in the app server. And I am running the extract from Designer studio not the command line.

Attached is log file. I appreciate your help

Capture.PNG

March 3, 2016 - 12:51pm
Response to SusheelKBonthala

For your extract rule could you post a screenshot of the "File Specification" tab.  For a csv extraction there is no DDL.  That is only for a DB extraction.  Are you generating a manifest and sending that to the database or have you just tried with csv and with db separately and just don't see the output file?

March 3, 2016 - 1:03pm
Response to CelesteDufresne_GCS

Yes, I have tried with csv and db separately. I could not get output for any of them. Attached are the screenshotsCapture1.PNGCapture.PNG

March 3, 2016 - 1:33pm
Response to SusheelKBonthala

Is the \\nasgwss0021pn.uhn.com your app server node?  If you run with just \pas\PASdev\BIX do you see the output in that directory? It isn't throwing an error that it cannot write to that output so it seems like it is writing it somewhere.  What specific version of Pega/BIX 7.1 is this?

March 3, 2016 - 1:43pm
Response to CelesteDufresne_GCS

Yes it is my node. But when I run with \pas\PASdev\BIX, it says no directory found.

Yes, it is writing somewhere but could not identify it in the given path. am using 7.1.6 of pega and 7.1 of Bix.

March 3, 2016 - 2:15pm
Response to SusheelKBonthala

You are saying it is your node but is it the node where the application server is actually running?  It seems like it is not the actual app server node as when you try to write to that directory it is telling you there isn't a directory /pas/PASdev/BIX

March 3, 2016 - 2:28pm
Response to CelesteDufresne_GCS

Actually I have the write access in the node physical folders, but I am not able to understand why the ddl is not getting saved into this node I specified. For, ddl, below is the screenshotCapture1.PNG

Pega
March 3, 2016 - 11:08pm
Response to SusheelKBonthala

So you are saying that even though on the screenshot it says creating schema file to "\\nasgwss0021pn.uhc.com\pas\PASdev\BIX.sql", there is no file called BIX.sql present? And there are no errors in BIX log file?

Also, DDL (schema) generation is not required if your extract type is CSV.

March 4, 2016 - 9:52am
Response to nistr

Yes, Actually we were trying with DB schema. So, Generated DDL for that purpose. The issue is resolved now.

The reason for that issue is we were trying to extract the records from the Framework layer rather than the Implementation layer. Thanks for your help Celeste and Rajiv.