I installed SAP Netweaver Application Server 7.52 SP04 on my virtual box, it's working fine.
I have created Z* master data table and populated it with 2 mock records.
I created datasource via transaction RSO2.
I replicated data source via transaction RSDS.
I created necessary infoobject and its attributes in Data Warehousing Workbench and activated it.
I added newly created infoobject from step 5) as data tarrget.
I created transformation for the data target from step 6) and activated it.
I created infopackage for the replicated data source and clicked "Start" button in the "Schedule" tab of my infopackage (with option "Start immediately")
I check the monitor for infopackage where it says:
"Data not received in PSA Table Diagnosis Data has not been updated in PSA Table . The request is probably still running or there was a short dump". (Please see screenshot below)
I checked for short dumps - there are none.
Some googling gave recommendation to establish trusted connection in SM59, which I did (Please see screenshot below- I was logged as BWDEVELOPER)
I ran "Start immediately" again in my infopackage and once again checked the monitor, now it says that I have no authorization to lig via trusted system. (Please see screenshot below)
The detailed warnings are like this: (Please see screenshot below)
How do I fix this? What am I doing wrong?
The issue is with tRFCs which were stuck in queue (SM58). After manually executing LUWs data goes to PSA tables just fine.
Related
The source is SQL Server 2016 and Target is Netezza 7.2
When a source table is being mapped to the target, The below message appears,
ERROR:
An error has occurred while setting the replication method for dbo.CCM [An error occurred while turning on supplemental logging for dbo.CCM.
Failed to get publication ID.]. Check the event log for related events and a possible cause.
SQL Server Replication is enabled with a local distributor database. We have checked the CDC event logs and the same error is logged, nothing much in detail.
Any help on this would be appreciated.
You need to check the trace files. These are located in whichever folder you selected for instance data in the install. If you do not know this you can look at /conf/userfolder.vmargs - /instance/log
If you cannot find any useful information, then turn on detailed traces
1.) Management Console, configuration perspective, select the MS SQL Server datastore, properties, system parameters
2.) Add a new parameter global_trace_hours and specify a numeric value say 4
3.) Save
4.) The tracing is enabled dynamically - tracing will be set on for the number of hours you specify. The value will be automatically decremented every minute and then when it gets to 0 tracing is automatically and dynamically disabled
5.) Attempt to change the replication method to mirror again
6.) In the folder /instance/log/on you should find some files with data in
7.) Copy the trace file to a location with a short path (e.g. C:\TEMP) - or if it has already been zipped, unzip to C:\TEMP
8.) Open a command prompt as administrator
9.) Change directory to /bin
10.) Execute dmdecodetrace C:\TEMP\ | more
Note that the additional trace files are not full text, to minimize the impact of writing them, so need to be decoded
If you still do not get any pointers open a support ticket.
One potential cause could be that the table does not have a primary key. SQL replication requires a primary key, and as CDC is using the SQL replication to ensure that the full row images are logged in the transaction log, it is also a prereq for CDC as well.
I've created a report in Pentaho Report Designer 6.0.1 with dependent parameters. Published the same to Pentaho BI Server 6.1. The report runs perfectly in the PRD in Preview and i'm able to see the data. Also, there are no errors thrown during publishing the report as well. But after publishing, when i try to launch the report, the link opens up blank with the loading spinner just rotating forever. I checked the logs in the biserver as well (catalina.out and pentaho.log), apart from 1 error during launch (java.io.UTFDataFormatException: encoded string too long: 78805 bytes), there is no other error seen. Not even during the report load.
Can someone please tell me what is going wrong here?
Check your SQL behind the report. I've had some similar problems whilst trying to run some reports from the server on 6.0.
The problem I faced had to do with me not manually typing the correct typecasts. e.g. active = 1 instead of active = TRUE (basically I was creating "bad" SQL's). After I made those changes they launched correctly again.
I'm facing an error with a .prpt file.
While running the prpt in report designer it just works fine .
But when the same prpt ran in PUC (user console), the report contents are not displayed.
It is a simple report containing total 8 columns with only text and number fields in the detail section and only labels (formulated also) in headers.
Please help with your valuable tips
Check the server logs - there'll be an exception. I've seen this before - frequently it is due to layout issues, not sure why but for some reason in some cases the server bombs, yet the client does manage to render it. Double check the obvious like overlapping elements etc.
Also check the version of your PRD client, and the exact version of the reporting libraries on the server, they MUST match.
I've seen this happen when you have a prpt file that was created in an older (or newer) version of PRD than the server. You'll get javascript errors and onscreen you'll just see a blank page/tab. Make sure your version of PRD matches the server version.
I have installed and configured SSRS using SharePoint integrated deployment mode and have been able to successfully run a report from SharePoint. I created a custom deployment application that will upload all reports and datasets as well as create all data sources and make the proper connections between them when necessary.
I have one report that failed and I need to manually mess with the reports connection to a data source but I found that the drop down does not contain the options to let me manage its shared data sources (see example below).
In this image you can see the option that I am missing. Please excuse the colors, this is the best image I could find online in a pinch.
This is only happening in one environment so there must be a configuration change I am not thinking of to show these options. Here are the things I have already checked:
The account I am using is in the sites Owners group and has full control of everything, including the report file.
The item is being uploaded as a Document content type for some reason, but I edited properties and changed that to Report Builder Report content type.
The Report Server Integration site collection feature has been activated.
All of the Reporting Service content types have been added to the list.
I would revert to deployment from BIDS to debug this issue. It will perform some validation during that process and possibly return meaningful errors.
So this turned out to be caused by one of our customizations. We had an old custom javascript function that was named the same as a SharePoint javascript function that has something to do with those drop down actions. Hope this helps someone else.
I am working on SQL 2008 - SSIS Package. I am executing the package from C# code. It's simple Flat File ( .csv) to SQL Table.
From the C# code, I get execution result as SUCCESS but inside the package Transactions have not taken, so values are not actually exported.
I need to debug it, by reading the log file.
How to create Error Log or Log File inside the Package?
Here is one way of configuring logging feature in SSIS. In this example, I have Send Mail Task configured to fail and I have enabled the SQL Server based logging which will store the OnError and OnTaskFailed messages when the package fails. There are other events that could be of interest to you as well. In the projects that I have worked, these two tasks have helped me to identify most of the issues that occur in SSIS packages.
Step-by-step process:
SSIS package in this example contains a Send Mail Task configured as shown in screenshot #1. It is configured to fail so we can see some error messages in the log table.
Click on the SSIS package.
On the menus, select SSIS --> Logging... Refer screenshot #2.
On the Configure SSIS Logs: dialog, select the provider type and click Add. I have chosen SQL Server for this example. Check the Name checkbox and provide the data source under Configuration column. Here SQLServer is the name of the connection manager. SSIS will create a table named dbo.sysssislog and stored procedure dbo.sp_ssis_addlogentry in the database that you selected. Refer screenshot #3 below.
If you need to capture the errors, select the checkbox OnError and OnTaskFailed. Refer screenshot #4 below.
Sample package execution within data flow task is shown in screenshot #5 below.
Sample output of the log table dbo.sysssislog is shown in screenshot #6 below. I have only displayed few columns id, event, source and message. There are other columns in the table. Message column contains the error message, here in this case the server name mentioned in the Send Mail Task is wrong. Source column contains the task where it failed. Here in this case, the package name is SSISLoggingExample and Send Mail Task is named as Email Task. Error messages will bubble up from task to the package level. Hence, the error message is logged twice under the task as well as at the package level.
Hope that helps.
Screenshot #1:
Screenshot #2:
Screenshot #3:
Screenshot #4:
Screenshot #5:
Screenshot #6:
It's very easy to log errors in SSIS. Go to Event Handlers tab, select OnError from dropdown. Now here you can send email on any error or you can develop your own custom logic to log error into DB or write to text file.
Also, you can choose from existing logging mechanism available in SSIS. Click on menu "SSIS", you will see first option as Logging then you will see different options to log errors/warnings and whole lot of information you need.