In one of the Oracle 19c databases any expdp or impdp command is failing with the below error
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user SYSTEM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1145
ORA-04045: errors during recompilation/revalidation of SYS.DBMS_LOGREP_UTIL
ORA-01775: looping chain of synonyms
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGREP_UTIL"
ORA-06512: at "SYS.KUPV$FT", line 957
I can see that the package SYS.DBMS_LOGREP_UTIL is in invalid state with the following errors in the screenshot
How can I resolve the error and compile the package. The package is wrapped so I cannot see the table which is throwing the looping chain of synonyms error
The issue got resolved after running catrep.sql and other related sqls in rdbms/admin directory.
Related
I have been trying to upgrade SQL server 2017 to run Python 3.7. We have installed CU28 and the product version is 14.0.3430.2 which includes the C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7.
I have made sure all permissions are granted to the INSTANCENAME directory and pythonlauncher.config working directory is pointing to C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData and launchpad service account has permissions to this directory.
I have done all this as an upgrade twice and got various errors, and a clean install. The error I am getting is
Msg 39004, Level 16, State 20, Line 0
A 'Python' script error occurred during execution of 'sp_execute_external_script' with HRESULT 0x80004004.
Msg 39019, Level 16, State 2, Line 0
An external script error occurred:
Invalid BXL stream
error while running BxlServer: caught exception: Error communicating between BxlServer and client: 0x000000e8
HRESULT 0x000000e8 looks like INVALID_CANCEL_OF_FILE_OPEN
HRESULT 0x80004004 looks like E_ABORT
So no real clues what is wrong here. pythonlauncher.log does show the error;
[Error] Process::TryTerminate failed with error code: 5
Session 0E93E9D1-07A7-448A-8B1A-FCA5263A5F53 TryTerminate(1067) failed with 5
Error code 5 is ERROR_ACCESS_DENIED
Also got this warning
[Warning] StaleDirectoryCleaner() failed to delete C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData\FAMSQL17UAT01\8B97815A-E9EA-4FA0-98F3-0440D4180522 after 5 retries
So all up this looks there are still permission issues. Extremely frustrating as there is next to no help on this. Any help would be greatly appreciated.
UPDATE:
After another clean install - first checked Python 3.5.2 worked and it did. Upgraded to 3.7, and again got the same issue. A bit more digging around I find this...
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SERVERNAME.domain_name.com:INSTANCENAME ]
Login failed for user 'DOMAIN\SERVERNAME$'. Reason: Could not find a login matching the name provided.
We have a service account that is not part of the domain which is NT Service\MSSQL$INSTANCENAME. Why on this implementation expecting a windows authenticated user the same name as the server??? How can I go about remedy this?
I think what has happened is that MS have left debug code in their production release.
FURTHER UPDATE:
In the event log we are seeing
Faulting application:Python.exe: 3.7.1150.1013 Faulting module name:
pylink.pyd Faulting module path:c:\Program Files\Microsoft SQL
Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7\lib\site-packages\revoscalepy\rxLibs\pylink.pyd
Microsoft have confirmed that this is a bug. Their work around is below.
It's CU27 and CU28 that 3.7 is broken in - so you could use CU26 and still use Python 3.7. That version started at CU22... so CU22-26 work fine.
Or - it's only the pylink.pyd that is broken - you can simply grab the pylink.pyd from a CU22-26 installation for Python 3.7, and swap it into your CU27/CU28 files. This workaround will work now, and will also not cause any issues going forward once the fix does come. That is, on your next update, it shouldn't interfere and it should all go smoothly.
I have an SSIS package that when I run them from within VS 2015 Update 3, fails on a step. I asked another developer to try running the package on his machine, and it works fine on his machine. He also has VS 2015 update 3.
[name of step] Error: The [name of step] was unable to process the data. Object reference not set to an instance of an object.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on [name of step] returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
I have tried repairing VS2015, but the issue still happens.
I installed Bugzilla on centos server ,But after installation it show error like below .I googled lot nothing works`
Software error:
The /var/lib/bugzilla/data/params file does not exist. You probably
need to run checksetup.pl. at Bugzilla/Config.pm line 344. Compilation
failed in require at /usr/share/bugzilla/index.cgi line 34. BEGIN
failed--compilation aborted at /usr/share/bugzilla/index.cgi line 34.
`
I'm trying to start a fresh install of TFS 2013 but running into the issue TF255356: The following error occurred when configuring the Team Foundation databases: TF400711: Error occurred while executing servicing step Create Warehouse for component InstallWarehouse during Install: Create Analysis Database schema failed: Error generating Analysis Database: File system error: The following error occurred while opening the file '\?\E:\TempDB\MDTempStore_1584_1_j1pv2.tmp': Access is denied.
I have tried to remove the read-only flag from the tempdb folder but it keeps getting set to true after applying the change. I have also added the registry entry UseSystemForSystemFolders which allows read-only to be removed from the folder but it does not persist.
Any help with this would be great
Thanks
Chris
I call from Jenkins the Sonar runner and then the following error occurs:
Fail to purge data [id=1]
org.apache.ibatis.exceptions.PersistenceException:
### Error updating database. Cause: java.sql.SQLException: Prepared or callable statement has more than 2000 parameter markers.
### SQL: delete from dependencies where from_snapshot_id in
...
### Cause: java.sql.SQLException: Prepared or callable statement has more than 2000 parameter markers.
Does any one knows a workaround of this error (Sonar bug).
Indeed this is known issue which should be quickly fixed but for the time being there is no workaround : http://jira.codehaus.org/browse/SONAR-4586 expect to downgrade to SonarQube 3.6.