Sql error code 1722

sql error code 1722

Looks like only Win10 for ARM image was able to install SQL Server 2019. I've installed SQL successfully. Component error code: 1722. This error is caused by the Oracle database when it is unable to convert a character string into a valid number. For more information about. If the server was registered before you created the alias, try deleting the server registration in EM and then re-register the server. I have a.

Sql error code 1722 - really

Microsoft distributes Microsoft SQL Server 2008 Service Pack 2 (SP2) or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 2 (SP2) or SQL Server 2008 R2 fix release.

Symptoms

Consider the following scenario:

  • You create a table that has a varchar (max) data type column in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2.

  • You try to replicate the table to an Oracle server subscriber, and you select Transactional publication as the publication type.

    Note The initial synchronization is successful.

  • You insert or update a long value record in the varchar (max) column of the table.

    For example, the value is more than 8200 characters long.


In this scenario, the Distribution Agent does not synchronize the new record to the Oracle server subscriber. Additionally, you receive the following error message:

Replication-Replication Distibution Subsystem: agent <agent name> failed. ORA-01722: invalid numberErrorId = 160, SourceTypeId = 16
ErrorCode = '1722'
ErrorText = 'ORA-01722: invalid number'

Resolution

Cumulative update information

SQL Server 2008 R2


The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2567713 Cumulative Update package 9 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1


The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2567714 Cumulative Update package 2 for SQL Server 2008 R2 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2


The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

2527180 Cumulative update package 4 for SQL Server 2008 SP2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 SP2 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about Oracle publishing, visit the following MSDN website:

General information about Oracle publishingFor more information about Oracle subscribers, visit the following MSDN website:

General information about Oracle subscribersFor more information about snapshot replication, visit the following MSDN website:

General information about snapshot replication

Read these next...

In the backend I'm getting data but it failed in PIA,

Please let me know solution for this challenge.
Return: 1722 - ORA-01722: invalid number Failed SQL stmt: INSERT INTO PS_H_BN_VS_STG SELECT J.EMPLID , N1.NATIONAL_ID , N1.COUNTRY , N1.NATIONAL_ID_TYPE , J.EFFDT , J.EMPL_STATUS , N.NAME_INITIALS , N.FIRST_NAME , N.LAST_NAME , N.NAME_ROYAL_PREFIX , N.PARTNER_LAST_NAME , N.PARTNER_ROY_PREFIX , N.LAST_NAME_PREF_NLD NAME_FORMAT , P.SEX , P.BIRTHDATE , ' ' BIRTHCITY , ' ' BBIRTHCOUNTRY , ' ' AS NATIONALITY , ' ' MAR_STATUS , A.ADDRESS1 STREET , A.COUNTRY ADRS_COUNTRY , A.NUM1 NUM ,A.POSTAL ,A.CITY ,NVL(( SELECT COUNTRY_2CHAR FROM PS_COUNTRY_TBL WHERE COUNTRY=(( SELECT C.COUNTRY FROM PS_CITIZENSHIP C WHERE C.EMPLID=J.EMPLID AND C.CITIZENSHIP_STATUS=1 AND C.DEPENDENT_ID=' '))),' ') COUNTRY ,NVL(( SELECT PH1.PHONE FROM PS_PERSONAL_PHONE PH1 WHERE PH1.PHONE_TYPE='HOME' AND PH1.EMPLID=J.EMPLID),' ') PHONE ,' ' FAX , NVL(( SELECT PH1.PHONE FROM PS_PERSONAL_PHONE PH1 WHERE PH1.EMPLID=J.EMPLID AND PH1.PHONE_TYPE='CELL'),' ') MOBILE , ' ' AS EMAIL ,NVL(( SELECT X.EFFDT FROM PS_JOB X WHERE X.EMPLID=J.EMPLID AND X.EFFDT=( SELECT MAX(X1.EFFDT) FROM PS_JOB X1 WHERE X1.EMPLID=X.EMPLID AND X1.EMPL_RCD=X.EMPL_RCD AND X1.EFFDT<=J.EFFDT) AND X.EFFSEQ= ( SELECT MAX(X2.EFFSEQ) FROM PS_JOB X2 WHERE X2.EMPLID=X.EMPLID AND X2.EFFDT =X.EFFDT AND X2.EMPL_RCD=X.EMPL_RCD) AND X.ACTION='XFR' AND X.ACTION_REASON='XFR'),J.LAST_HIRE_DT) START_DATE , CASE WHEN J.ACTION IN ('TER' , 'RET') THEN J.TERMINATION_DT ELSE NULL END CHANGEDATE ,CASE WHEN J.ACTION IN ('TER' , 'RET') THEN J.EFFDT ELSE NULL END TERMINATION_DT , J.ACTION ,J.ACTION_REASON ,J.ACTION_DT ,J.COMPANY ,' ' EMPLOYER_NAME , J.DEPTID ,J.SETID_DEPT ,' ' DEPT_NAME ,J.REG_TEMP ,J.JOBCODE ,J.SETID_JOBCODE ,' ' JOBCODE_DESCR , NVL(( SELECT X.STD_HOURS FROM PS_SAL_PLAN_TBL X WHERE X.SETID=J.SETID_SALARY AND X.SAL_ADMIN_PLAN=J.SAL_ADMIN_PLAN AND X.EFFDT =(SELECT MAX(X1.EFFDT) FROM PS_SAL_PLAN_TBL X1 WHERE X.SETID=X1.SETID AND X.SAL_ADMIN_PLAN=X1.SAL_ADMIN_PLAN)),0) AS WEEKLY_HOURS , J.STD_HOURS AS ACTUAL_WEEKLY_HRS , J.STD_HRS_FREQUENCY ,6 AS SALARY_PERIOD ,J.ANNUAL_RT AS SALARY , J.DEPTID AS COSTCENTER , J.LOCATION , ' ' NO_RISK , ' ' IBAN , J.SUPERVISOR_ID , ' ' EMAIL_MANAGER , M.H_HRBP_EID AS HRG_MAANGER , ' ' EMAIL_HRG ,' ' HRG_FOREIGN FROM PS_JOB J , PS_NAMES N , PS_PERSONAL_DATA P , PS_ADDRESSES A ,PS_H_HR_MANAGR_TBL M ,PS_PERS_NID N1 WHERE M.EMPLID=J.EMPLID AND N1.EMPLID=J.EMPLID AND J.PER_ORG='EMP' AND N.EMPLID=J.EMPLID AND N1.PRIMARY_NID='Y' AND J.EFFDT= ( SELECT MAX(J1.EFFDT) FROM PS_JOB J1 WHERE J1.EMPLID=J.EMPLID AND J1.EMPL_RCD=J.EMPL_RCD AND J1.EFFDT <=SYSDATE ) AND J.EFFSEQ= ( SELECT MAX(J2.EFFSEQ) FROM PS_JOB J2 WHERE J2.EMPLID=J.EMPLID AND J2.EFFDT =J.EFFDT AND J2.EMPL_RCD=J.EMPL_RCD) AND M.EFFDT=( SELECT MAX(M1.EFFDT) FROM PS_H_HR_MANAGR_TBL M1 WHERE M1.EMPLID=M.EMPLID AND M1.EMPL_RCD=M.EMPL_RCD AND M1.EFFDT<=SYSDATE) AND M.EMPL_RCD=J.EMPL_RCD AND J.REG_REGION='NLD' AND P.EMPLID =J.EMPLID AND A.EMPLID =J.EMPLID AND A.ADDRESS_TYPE='HOME' AND A.EFFDT =( SELECT MAX(A1.EFFDT) FROM PS_ADDRESSES A1 WHERE A1.EMPLID =A.EMPLID AND A1.ADDRESS_TYPE=A.ADDRESS_TYPE AND A1.EFFDT<=SYSDATE) AND N.NAME_TYPE='PRI' AND N.EFFDT=( SELECT MAX(N1.EFFDT) FROM PS_NAMES N1 WHERE N1.EMPLID=J.EMPLID AND N1.NAME_TYPE =N.NAME_TYPE AND N1.EFFDT<=J.EFFDT) AND ((J.EMPL_STATUS IN ('A' ,'L','P','S') AND J.HR_STATUS ='A') OR (J.EMPL_STATUS IN ('D','Q','R','T','U') AND J.HR_STATUS ='I') ) AND J.EMPL_CLASS IN ('M','I','T','C','W','B','H','J','L') AND (J.ACTION <> 'TER' OR (J.ACTION = 'TER' AND (J.ACTION_DT > = (SYSDATE-10)) ) OR j.effdt > = (SYSDATE-10))

  • Several possibilities:

    (a) SQL was too busy being quietly sick in a corner.

    (b) SYSDATE is of type DATE, and you can't do arithmetic on it like (SYSDATE-10). You have to use a function on it to deal with the internal format.

    (c) The last test separates >= into > = which is a syntax bug (might be down to the site's formatting, which always sucks).

    (d) Some of your data columns might be non-numeric or null.

  • @Paul

    (a) It ain't pretty, but I've seen worse SQL. Error does not support this

    (b) Oracle can do simple arithmetic to dates.  Not an issue

    (c) Oracle can handle a space between the operators.  Not an issue

    @OP

    (d) most likely issue, probably have a column flipped between the SQL and Stage table or incorrectly set one of the values to an incorrect type.

    J

  • Justin,

    OK, the comment about SQL up-chucking was out of order. What I meant to say was: "It is generally a bad idea to write something you can't debug."

    This quote is from Brian Kernighan (who knew a thing or two) in his book "The Elements of Programming Style".

    "Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?"



  • @Paul

    I agree.  Ugly SQL makes me a sad panda.

    @OP

    Run your select statement in an SQL Editor (like PL/SQL, Toad, etc) and match the columns to your staging table fields, then use your Mark I eyeball to find any discrepancies.

    J


  • Showing End Users How The Sausage Is Made

    Showing End Users How The Sausage Is Made

    Best Practices & General IT

    Basic scenario is this1 - End user submits issue via email2 - IT investigates and proves issue is with external vendor3 - IT emails vendor4 - Vendor emails back5 - repeat 3+4 until issue is fixed6 - IT emails end user to say it's fixed, or details how to ...

  • MS is finally introducing Server licensing by Virtual Core

    MS is finally introducing Server licensing by Virtual Core

    Software

    Details are still a bit thin, but they say it will be starting on October 1st.With the virtual core licensing option, customers can elect to license Windows Server by the number of virtual cores they are using in virtual machines, making Windows Server ea...

  • Warning for players of Genshin Impact on PC......

    Warning for players of Genshin Impact on PC......

    Security

    I personally have never played this but I know people who do.  I wonder how long until it's fixed.  Would you uninstall a game because of a possible security issue?https://hackaday.com/2022/08/29/genshin-security-impact/

  • Spark! Pro Series - 30 August 2022

    Spark! Pro Series - 30 August 2022

    Spiceworks Originals

    Good morning and welcome to the penultimate Spark! of August 2022. The year seems to be just flying by. Here in Upstate New York the Great New York State Fair is underway, a sure sign that the summer is almost over. If ...

  • Snap! Nitrokod malware, backups, Zen 4 CPUs, Artemis 1, Gamescom wrap-up, etc.

    Snap! Nitrokod malware, backups, Zen 4 CPUs, Artemis 1, Gamescom wrap-up, etc.

    Spiceworks Originals

    Your daily dose of tech news, in brief. There were at least a handful of big events in the summer of 1969, including the Apollo 11 landing. Yet another event occurred that summer, one that the public hardly noticed, but it has proven to have a last...

KB4530084 - FIX: Error occurs when you try to install SQL Server 2019 on a low power CPU

Symptoms

Assume that you try to install SQL Server 2019 on a low power CPU. In this situation, SQL Server installation may fail because of service installation time-out.

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. 

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

This issue is fixed in the following cumulative update for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References

Learn about the terminology that Microsoft uses to describe software updates.

SQL install script error: System.Data.SqlClient.SqlException (0x80131904): The operation cannot be performed on database "<DB_Name>" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

ALTER DATABASE statement failed.

 

ST.DatabaseConfiguration.log error scenario 2

DatabaseInstaller.cs:928

Purpose

 

The purpose of this documentation is to provide additional information and resolutions when the installation of Protect 9.X fails with 'Error 1722'.

 

 

Error in Protectupdate*.log located in the %temp% directory shows "Error 1722"

 

MSI (s) (2C:C0) [17:53:28:738]: Note: 1: 1722 2: SetupDatabaseAction 3: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe 4: -quiet -upgrade -consoleId <GUID> -timeout 1800

CustomAction SetupDatabaseAction returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (2C:C0) [17:53:32:763]: Product: Shavlik Protect -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SetupDatabaseAction, location: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe, command: -quiet -upgrade -consoleId <GUID> -timeout 1800

 

The error occured while running ST.DatabaseConfiguration.exe.

Checking the ST.DatabaseConfiguration.log shows one of the following errors:

 

ST.DatabaseConfiguration.log error scenario 1

DatabaseInstaller.cs:561

ORA-01722: invalid number tips

       ORA-01722 invalid number
 
Cause: The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.
 
Action: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.

Jonathan Gennick provides information regarding Oracle ORA-01722 in conjunction with subqueries and Oracle Optimizer. 

To exhibit how Oracle ORA-01722 is often thrown, this query is given as an example:

SELECT *
FROM ( SELECT FLAG, TO_NUMBER ( NUM ) NUM
FROM SUBTEST
WHERE FLAG = 'N' )
WHERE NUM > 0 ;

Here, from in the FROM clause of a query, the user is attempting to have a subquery of the original query, which is causing Oracle ORA-01722 to be thrown. 

The Oracle ORA-01722 error is thrown with the failure because  of the outer query.  This is because it is trying to test the NUM > 0 condition first because it is assumed it might be more useful. 

Gennick goes on to show that Oracle ORA-01722 is thrown because the Oracle optimizer has re-written the query as:

SELECT FLAG, TO_NUMBER ( NUM ) NUM
FROM   SUBTEST
WHERE  TO_NUMBER ( NUM ) > 0
AND    FLAG = 'N' ;

This throws Oracle ORA-01722 because the re-written query causes the system to convert a non-numeric NUM value of the WHERE clause into numbers.

OraFaq also has notes on Oracle ORA-01722.  Here, it is explained that Oracle ORA-01722 is thrown because a particular string was not able o be converted into a specific valid number when a user attempted to convert a character string. 

There are several possible resolutions to Oracle ORA-01722 in this context:

  • If you are attempting an " INSERT INTO ... VALUES (...) " you need to find out which data item is invalid
  • If you are trying to supply the values in a sub query which is intended to INSERT or UPDATE, you have to dig a little beeper because the character that is throwing ORA-01722 is actually hidden.  You would then need to find the row that contains a non-numeric string.  Then, you should fix or add data to resolve ORA-01722
  • Instead of an INSERT or UPDATE, you attempt a SELECT.  Here, ORA-01722 is thrown most likely because of some implicit conversation in WHERE.  To resolve ORA-01722 in this context, find a numeric and character column which are being compared.

For more information on Oracle ORA-01722 see these links:

ORA-01722 - Oracle DBA Forums

ORA-01722: invalid number


 

sql error code 1722

Idea: Sql error code 1722

Stop unknown hard error windows xp
Centos 6.2 kernell error
Log c+ + domain error
LOADING ILPATCH ERROR
BAD CMOS CHECKSUM ERROR

You can watch a thematic video

How To Fix Error 1722 There Is A Problem With This Windows Installer Package Windows 7 / 8 / 10

Sql error code 1722 - are mistaken

Purpose

 

The purpose of this documentation is to provide additional information and resolutions when the installation of Protect 9.X fails with 'Error 1722'.

 

 

Error in Protectupdate*.log located in the %temp% directory shows "Error 1722"

 

MSI (s) (2C:C0) [17:53:28:738]: Note: 1: 1722 2: SetupDatabaseAction 3: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe 4: -quiet -upgrade -consoleId <GUID> -timeout 1800

CustomAction SetupDatabaseAction returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (2C:C0) [17:53:32:763]: Product: Shavlik Protect -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SetupDatabaseAction, location: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe, command: -quiet -upgrade -consoleId <GUID> -timeout 1800

 

The error occured while running ST.DatabaseConfiguration.exe.

Checking the ST.DatabaseConfiguration.log shows one of the following errors:

 

ST.DatabaseConfiguration.log error scenario 1

DatabaseInstaller.cs:561

Error 1722 - (The RPC server is unavailable) occurred while...

I get the same error

I don't have any idea; but I can tell you my situation.

Firstly, all my instances are named in the way you said; servername\instancename.

I can create an alias and have made more than one alias to the same instance - reasons follow.

I found a few days ago, I could not register the instance, after its removal from the server group it had been under; so far I have only been able to reconnect via an alias. This was after removal of an un-needed instance, using the install program, and running servicepak 4 (sql server 2000) again.

Now this is what is strange; my named pipes alias doesn't get the problem (you described), but my alias that uses local host DOES. That is; an alias using TCP, 127.0.0.1\instancename registers, but after running servicepak 4 get the error you discuss.

Sorry if this just muddies it all,

David

Strangely, only 7 of 13 usual scripts run on the instance I'm trying to re-register when I run servicepak 4.

Error Oracle -1722 Invalid number after migrating DataServer to OE 11.7

Steps to Reproduce

/* Simulate the Development environment */ 1. Load FOO_Compile.sql into Oracle database. 2. Create an empty db "sh_compile.db" (logical name: sh) 3. Create Oracle DataServer schema and pull "foo" table 4. Run/Compile ABL statement (query.p) CREATE FOO. ASSIGN FOO.MYCHARFIELD = "ABCDE" FOO.MYNUMFIELD = 12345. RELEASE FOO. DataServer log with -Dsrv logentrytypes,SQL:4 reads: ORA SQL the SQL statement SELECT /*+ ROWID(T0) */ * FROM OE11.FOO T0 ORA SQL the SQL statement INSERT INTO OE11.FOO (MYCHARFIELD,MYNUMFIELD) VALUES (:X1, :X2) RETURNING ROWID INTO :rid ORA SQL Bind Mode call OCIBindByName: Column name=X1, value=ABCDE ORA SQL Bind Mode call OCIBindByName: Column name=X2, value=12345 ORA SQL Bind Mode call OCIBindByName: Column name=:rid, value= /* Simulate runtime environment */ 5. Load FOO_Runtime.sql into Oracle database 6. Create an empty db "sh_runtime.db" (logical name: sh) 7. Create Oracle DataServer schema and pull "foo" table 8. Run the COMPILED version of the procedure generated in step 4 () DataServer log with -Dsrv logentrytypes,SQL:4 will now show the MYNUMFIELD is assigned a *character* value.

SQL install script error: System.Data.SqlClient.SqlException (0x80131904): The operation cannot be performed on database "<DB_Name>" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

ALTER DATABASE statement failed.

 

ST.DatabaseConfiguration.log error scenario 2

DatabaseInstaller.cs:928

ORA-01722: invalid number tips

       ORA-01722 invalid number
 
Cause: The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.
 
Action: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.

Jonathan Gennick provides information regarding Oracle ORA-01722 in conjunction with subqueries and Oracle Optimizer. 

To exhibit how Oracle ORA-01722 is often thrown, this query is given as an example:

SELECT *
FROM ( SELECT FLAG, TO_NUMBER ( NUM ) NUM
FROM SUBTEST
WHERE FLAG = 'N' )
WHERE NUM > 0 ;

Here, from in the FROM clause of a query, the user is attempting to have a subquery of the original query, which is causing Oracle ORA-01722 to be thrown. 

The Oracle ORA-01722 error is thrown with the failure because  of the outer query.  This is because it is trying to test the NUM > 0 condition first because it is assumed it might be more useful. 

Gennick goes on to show that Oracle ORA-01722 is thrown because the Oracle optimizer has re-written the query as:

SELECT FLAG, TO_NUMBER ( NUM ) NUM
FROM   SUBTEST
WHERE  TO_NUMBER ( NUM ) > 0
AND    FLAG = 'N' ;

This throws Oracle ORA-01722 because the re-written query causes the system to convert a non-numeric NUM value of the WHERE clause into numbers.

OraFaq also has notes on Oracle ORA-01722.  Here, it is explained that Oracle ORA-01722 is thrown because a particular string was not able o be converted into a specific valid number when a user attempted to convert a character string. 

There are several possible resolutions to Oracle ORA-01722 in this context:

  • If you are attempting an " INSERT INTO ... VALUES (...) " you need to find out which data item is invalid
  • If you are trying to supply the values in a sub query which is intended to INSERT or UPDATE, you have to dig a little beeper because the character that is throwing ORA-01722 is actually hidden.  You would then need to find the row that contains a non-numeric string.  Then, you should fix or add data to resolve ORA-01722
  • Instead of an INSERT or UPDATE, you attempt a SELECT.  Here, ORA-01722 is thrown most likely because of some implicit conversation in WHERE.  To resolve ORA-01722 in this context, find a numeric and character column which are being compared.

For more information on Oracle ORA-01722 see these links:

ORA-01722 - Oracle DBA Forums

ORA-01722: invalid number


 

SQL or data conversion error. Failed to execute the installation.: System.Data.SqlClient.SqlException (0x80131904): Only members of the sysadmin role or the database owner may set the database compatibility level.
Please note it may be necessary to perform the upgrade using an account with the sysadmin role in the event the account you are using now, is not the same one that originally created the database.

 

 

Shavlik Protect 9.X

0 Comments

Leave a Comment