i'm using SonarQube Developer edition 7.3 with SonarScanner 3.2. During parsing my T-SQL code i've some errors like
WARN: Unable to parse file 'xxxxx.sql' : Parse error at line 7 column 4:
1:
2:
3:
4:
5:
6: CREATE TRIGGER [xxxx]
7: ON DATABASE
^
WARN: Unable to parse file 'xxxx.sql' : Parse error at line 34 column 16:
34: WITH NOWAIT, SETERROR;
Thanks
Giuseppe
I have got same problem too me. I don't understand anything from log messages.
Related
When trying to apply datapatch 31312468 to oracle 12.2.0.1 get the following:
Error at line 8833: 4675/23 PLS-00302: component 'ISNONORACLECLOUD' must be declared
Any ideas?
upd:
Datapatch Build label: RDBMS_12.2.0.1.0DBAPR2019RU_LINUX.X64_190227
Datapatch output: (for different patch, but it is exactly the same)
./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Thu Jul 23 11:27:05 2020
Copyright (c) 2012, 2019, Oracle. All rights reserved.
Log file for this invocation: /local/oracle/cfgtoollogs/sqlpatch/sqlpatch_541_2020_07_23_11_27_05/sqlpatch_invocation.log
Connecting to database...OK
Bootstrapping registry and package to current versions...done
Determining current state...done
Current state of SQL patches:
Patch 26635944 ():
Not installed in the binary or the SQL registry
Patch 29249637 (OJVM RELEASE UPDATE: 12.2.0.1.190416 (29249637)):
Installed in the binary registry only
Bundle series DBRU:
ID 190416 in the binary registry and not installed in the SQL registry
Adding patches to installation queue and performing prereq checks...
Installation queue:
Nothing to roll back
The following patches will be applied:
29249637 (OJVM RELEASE UPDATE: 12.2.0.1.190416 (29249637))
29314339 (DATABASE APR 2019 RELEASE UPDATE 12.2.0.1.190416)
Installing patches...
Patch installation complete. Total patches installed: 2
Validating logfiles...
Patch 29249637 apply: SUCCESS
logfile: /local/oracle/cfgtoollogs/sqlpatch/29249637/22802302/29249637_apply_ORCL_2020Jul23_11_27_18.log (no errors)
Patch 29314339 apply: WITH ERRORS
logfile: /local/oracle/cfgtoollogs/sqlpatch/29314339/22821655/29314339_apply_ORCL_2020Jul23_11_27_19.log (errors)
Error at line 3715: Warning: Package Body created with compilation errors.
Error at line 32330: Warning: Package Body created with compilation errors.
Error at line 32337: 4675/4 PL/SQL: Statement ignored
Error at line 32338: 4675/23 PLS-00302: component 'ISNONORACLECLOUD' must be declared
Error at line 32360: 4675/4 PL/SQL: Statement ignored
Error at line 32361: 4675/23 PLS-00302: component 'ISNONORACLECLOUD' must be declared
Error at line 33014: Warning: Trigger created with compilation errors.
Error at line 33021: 0/0 PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid
Error at line 33038: Warning: Trigger created with compilation errors.
Error at line 33045: 0/0 PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid
Error at line 33052: Warning: Trigger created with compilation errors.
Error at line 33059: 0/0 PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid
Please refer to MOS Note 1609718.1 and/or the invocation log
/local/oracle/cfgtoollogs/sqlpatch/sqlpatch_541_2020_07_23_11_27_05/sqlpatch_invocation.log
for information on how to resolve the above errors.
SQL Patching tool complete on Thu Jul 23 11:27:47 2020
Worked around loading the following objects prior to running datapatch:
$ORACLE_HOME/rdbms/admin/dbmsgwmco.sql
$ORACLE_HOME/rdbms/admin/dbmsgwmut.sql
$ORACLE_HOME/rdbms/admin/dbmspool.sql
I have instance of elasticsearch v7.0.0 running and when kibana v7.0.0 is started, the server logs show "Server running at http://localhost:5601" but the UI fails to load with error "Kibana did not load properly. Check the server output for more information" .
Please help provide pointers on above issue. Thanks.
kibana server log:
log [12:00:39.240] [info][status][plugin:maps#7.0.0] Status changed from yellow to green - Ready
log [12:00:39.487] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active
log [12:00:41.441] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml
log [12:00:41.594] [info][status][plugin:reporting#7.0.0] Status changed from uninitialized to green - Ready
log [12:00:41.634] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: Error: Failed to launch chrome!
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 1: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: cannot create qWqtq?q?q?q?qrr8rUrkryr?r?r?r?r?r?r?rs!s3sBsfs~s?s?s?s?sttAt?t?t?t?t?t?t?t?t?t?t?tuu:uKuYuqu~u?u?u?u?u?u?u?uv"v5vKvbvkvpvtvxv?v?vNw?????.???????)?B?S?c?w???????????????
??1?<?I?U?j?s?}?????¦¦%?/?;?L?o?w?~?????????????????????????????A??????????
??3? ???"???5?<?F?P?q????ggm
vm
5?
??
??
??C?\v?!?[? D?!!P)T!!??!!??41!!???b!!?R?!!0??!!???.x!!?>??!#?: File name too long
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 1: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: l?l?l?l?l?l?l?p?pqqqqq: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 1: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: : not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 7: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: !!???: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 8: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: !!????: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 1: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell:ELF: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 9: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell:!!??*!!???Q!!?????!HY?: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 9: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: !!????!!X??!!p?N!!81??: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 10: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: ?: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 11: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: !!8??l!: not found
/home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: 1: /home/test/kibana-7.0.0-linux-x86_64/data/headless_shell-linux/headless_shell: Syntax error: Unterminated quoted string
Here is a discussion forum for this issue.
I was facing the same issue, what I did was added libnss3 package on my ubuntu machine.
sudo apt-get install libnss3-dev
This helped me to get rid of the error.
I'm trying to perform a schema compare using the latest VS 2019 and SSDT tools.
However, two errors appear, which both start with:
An error occurred while attempting to reverse engineer elements of type
If I do the same SQL compare from VS 2017, there are no errors.
The first is:
Severity Code Description Project File Line Suppression State
Error An error occurred while attempting to reverse engineer elements of type Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlDatabaseCredential: Batch Command during reverse engineer failed with Error Code: -2146232060 Line Number: 7 Error Message:
Incorrect syntax near 'HINT'.
Incorrect syntax near 'HINT'.
...
Incorrect syntax near 'HINT'.
Incorrect syntax near 'HINT'.. 0
And the second is:
Severity Code Description Project File Line Suppression State
Error An error occurred while attempting to reverse engineer elements of type Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlErrorMessage: Batch Command during reverse engineer failed with Error Code: -2146232060 Line Number: 15 Error Message:
Incorrect syntax near 'HINT'.
Incorrect syntax near 'HINT'.
...
Incorrect syntax near 'HINT'.
Incorrect syntax near 'HINT'.. 0
I had the same error. Schema comparison from VS2019 to SQL Server 13.0.x failed. It worked properly with other SQL Server instances (other versions).
I applied all updates on SQL server up to 13.0.5292.0, and it works like a charm.
I'm following the Adapting Default Acoustic model tutorial and have hit a error running mllr_solve.
INFO: main.c(382): -- 1. Read input mean, (var) and accumulation.
ERROR: "pio.c", line 434: fread() failed; retrying...
: No error
ERROR: "swap.c", line 79: error while reading bo_magic
ERROR: "s3io.c", line 177: Error reading byte order magic number
ERROR: "s3io.c", line 265: Error reading header for en-us-8khz\means
FATAL: "main.c", line 392: Couldn't read en-us-8khz\means
I compiled sphinxtrain and sphinxbase using Visual Studio 2017 using 'Release\Win32'.
Is there anyway to change the means/variances files or change s3io.c?
This issue is most likely caused by runtime incompatibility between sphinxbase and sphinxtrain. Time to blame Windows designers, not software
https://cmusphinx.github.io/wiki/faq/#q-pocketsphinx-crashes-on-windows-in-_lock_file
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0246: The type or namespace name 'SD' could not be found (are you missing a using directive or an assembly reference?)
Source Error:
Line 25: using App2.DAL.ValidatorClasses;
Line 26:
Line 27: using SD.LLBLGen.Pro.ORMSupportClasses;
Line 28:
Line 29: namespace App2.DAL.EntityClasses
Source File: c:\inetpub\wwwroot\App_Code\App2.DAL\DatabaseGeneric\EntityClasses\ListI9DocsEntity.cs Line: 27
You need to check your references to LLBLGen ORMSupportClasses assembly in your asp.net project. Make sure the dll is copied to the output /bin directory.
BTW, ask your questions on the LLBLGen Forums, as they are monitored every day by the support team.