Byte representation of numbers in PL/SQL

Hello

I develop a customer SMPP (short Message Peer to Peer) in PL/SQL (10g) and I don't know how to convert numbers in the format requested by the specification of the Protocol (v 3.4).
(If someone is enterested, the specification document can be found here: here )

According to the specification, the numbers should be represented as "a value unsigned with the number of bytes (in our case, 4 bytes). The bytes will be always sent MSB first (Big Endian)".

So far, I found two examples of code on the Internet, showing one in PHP and one in Java.

In the PHP example, integers are transformed by the function 'pack' in unsigned long (always 32 bit, big endian byte order), then the result is written to the socket. The code where it is:

$header = pack ("NNNN" $v1, $v2, $v3, $v4);
fwrite ($this-> _socket, $header, 16);

In the java example, numbers are arranged in arrays of bytes by using the following code:

int OCTET_MASK = 0xff;
int i = (int) data;
Byte [] intBuf = new ubyte [4];
intBuf [3] = (byte) (I & OCTET_MASK);
intBuf [2] = (byte) ((i >>> 8) & OCTET_MASK);
intBuf [1] = (byte) ((i >>> 16) & OCTET_MASK);
intBuf [0] = (byte) ((i >>> 24) & OCTET_MASK);

They are then concatenated into a byte [] array and then again written to the socket.

Is there a way to get this functionality with PL/SQL?

Thank you in advance,

Max

Hello

I did a simple function that convert a value (the parameter num) in 4 bytes (big-endian):

CREATE OR REPLACE FUNCTION to4bytes (num IN NUMBER)
   RETURN RAW
IS
   byte4          RAW (4);
   hexstr         VARCHAR2 (8) := NULL;
   numtoconvert   NUMBER;
BEGIN
   numtoconvert := num;
   hexstr := SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1);
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   numtoconvert := TRUNC (numtoconvert / 16);
   hexstr :=
          SUBSTR ('0123456789ABCDEF', 1 + MOD (numtoconvert, 16), 1)
          || hexstr;
   byte4 := HEXTORAW (hexstr);
   RETURN byte4;
END;
/

The gross value represents what you want (4 bytes).
To be honest that an only small piece of what you try to do. Can now read documentation on UTL_TCP package...
http://download.Oracle.com/docs/CD/B19306_01/AppDev.102/b14258/u_tcp.htm

Published by: user11268895 on July 18, 2010 22:52

Tags: Database

Similar Questions

rounding of numbers in pl\sql

Hi, is there a way to round off numbers in pl\sql?

Maybe you are looking for an EYE.

with testdata as (select level/3-2 num from dual connect by level<=15)
select num, round(num), ceil(num)
from testdata;

NUM    ROUND   CEIL
------------------------------------------------
-1,67     -2     -1
-1,33     -1     -1
-1     -1     -1
-0,67     -1     0
-0,33     0     0
0     0     0
0,33     0     1
0,67     1     1
1     1     1
1,33     1     2
1,67     2     2
2     2     2
2,33     2     3
2,67     3     3
3     3     3

the set of values (numbers) in PL/SQL

Hello
I write a query in a stored (within a package) procedure, that the following condition is part of the query
```
WHERE dept_id IN (1,2,3)
```
I want to set the Group (1,2,3) as part of the declaration, it is later used by many parts of the package.
The question is, what is the easiest solution - as appropriate - to implement which...
something in pseudo-code as:
```
CONSTANT DEPT_SET = (1,2,3);
..................
.................
WHERE dept_id IN DEPT_SET
```
Thank you

1. create the SQL type:

create or replace

type NumList

in the table of the number

/

2. create the constant package:

constant dept_set NumList: = NumList (1,2,3);

3. Member use in where clause:

Dept_id WHERE MEMBERS OF DEPT_SET

SY.

Problem of NUMBERS in PL/SQL data type

DECLARE
num_ NUMBER (5.2);
BEGIN
num_: = 7555.554;
dbms_output.put_line (num_);
END;
I had a mistake in this program. How can I fix this and what is the theory for it?
Thanks in advance.

Hello

NUMBER (5, 2) means the number can have 5 digits, of which 2 are after the comma. Don't let that 5-2 = 3 digits before the comma, and the largest NUMBER, you can store is 999.99.

Is there a reason to limit the number of digits? If so, change the definition of ISSUE (6, 2) or (7, 3) to avoid rounding 7555.554. If you have no reason to limit the number of digits, just a NUMBER, like this:

DECLARE

num_ NUMBER;

BEGIN

...

Post edited by: FrankKulash
Changed (6, 3) to (7: 3) after the message below.

Number displayed in the oracle.sql.NUMBER form in the result of the query
Developer SQL version 3.2.10.09.57 displays numbers like "oracle.sql.NUMBER@66a35419 (the part after @ is not constant and change each time) even for simple count (*) select double."
At the same time "run the Script (F5)" no indication that the header
COUNT (*)
------------
and no the query results.
Hi Andriy,

The forum search, I see a similar complaint noted against 3.1.07.42. Instruction execution produces the list oracle.sql.NUMBER, probably because of a corrupt installation query results (due to decompress questions, or perhaps no decompression in an empty directory). See the following thread:
SQLDev 3.1: Number-fields in the tables have "oracle.sql.NUMBER @...". »

Hope this helps,
Gary
SQL development team

Graphical dial SQL Question
I am tiring to create a graph of numbering using this SQL and get an error "failed to parse the SQL query!
```
select 
   SNAPSHOT_EXEC_TIME_S value,
   500 maximum_value,
   2 low_value,
   79 high_value
from 
   (select SNAPSHOT_EXEC_TIME_S from STATS$SNAPSHOT order by SNAP_ID desc)
where rownum = 1
```
I also tried with the same error:
```
select 
   SNAPSHOT_EXEC_TIME_S,
   500
from 
   (select SNAPSHOT_EXEC_TIME_S from STATS$SNAPSHOT order by SNAP_ID desc)
where rownum = 1
```
I think it has to do with "rownum = 1", but not sure.

I'm on 4.0.2.00.07 and database 11.1.0.6 Apex

Published by: Sky13 on February 10, 2012 10:46 extra comma deleted after 500
I tried your first query on Apex 3.2, and it created a beautiful graphical dial.

Is there an error ORA-xxxxx with the message "failed to parse the SQL query? Did you check the spelling of the name of table & column?

P.S. The second query is not valid (a superfluous comma after the second column).

How to convert a single byte in UTF8 characters
Hello
I have problem with the export of data to the file with UTF8 encoding.

I varchar2 columns in the database with NLS_CHARACTERSET = EE8ISO8859P2 (Czech Republic) and I need to export the columns in the file with UTF8 encoding.

So I need to make a single byte FOR byte conversion multi.

I tried sql CONVERT (CONVERT ('my_char', 'UTF8') command) in the forms, but without effect. The encoding of the file created is UTF8, but the characters are corupted.

Registry settings on my client is NLS_LANG = REPUBLIC of AMERICAN_CZECH. EE8MSWIN1250

Could you tell me some thing how to export data from the column with characters on a single byte of file with UTF8 encoding?

I use Text_io package to write in the shapefile.

Thank you
my last try so if you can afford an empty space in your output file in the fist line. I tested hv it works

create a foo.txt with empty space and then add the file as a normal procedure or try to re - open the file later and replace the space in the first row using SUBSTR etc etc.

TEXT_IO has very limited functionality try to package DDE it might solve your problem

Good luck
Bangoura

Why I have an execution plan

Hello
I do not understand why this sql has a bad execution plan?
SELECT DISTINCT LETTER0_. LE_IDENT AS col_0_0_
THE LETTER LETTER0_
LEFT OUTER JOIN CONTEXT1_ CONTEXT
ON LETTER0_. LE_PTRCTXID = CONTEXT1_. CTX_IDENT
LEFT OUTER JOIN F_DOC f_doc2_
ON LETTER0_. LE_PTRDOCID = f_doc2_. DOC_IDENT
WHERE LETTER0_. LE_IDENT IN
(SELECT LETTER3_. LE_IDENT
THE LETTER LETTER3_, CONTEXT CONTEXT4_
WHERE LETTER3_. LE_PTRCTXID = CONTEXT4_. CTX_IDENT
AND CONTEXT4_. CTX_PTRPOLID = 400728434)
OR LETTER0_. LE_IDENT IN (2525432);
Execution plan
----------------------------------------------------------
0 SELECT optimizer Mode STATEMENT = ALL_ROWS (cost = card 175 = 14 K bytes = 83 K)
1 FILTER 0
2 1 INDEX FULL SCAN PROSHIVA1. PK_LE_CLE (cost = card 175 = 284 K bytes = 1 M)
3 1 LOOPS IMBRIQUEES (cost = 4 cards = 1 bytes = 22)
TABLE 3 ACCESS BY INDEX ROWID PROSHIVA1 4. F_LETTRES (cost = 2 card = 1 bytes = 13)
5 4 INDEX UNIQUE PROSHIVA1 SCAN. PK_LE_CLE (cost = 1 card = 1)
6 TABLE ACCESS BY INDEX ROWID PROSHIVA1 3. F_CONTEXT (cost = 2 card = 1 bytes = 9)
7 6 INDEX RANGE SCAN PROSHIVA1. IND_CTX_PTRPOLID (cost = 1 card = 1)
Statistics
----------------------------------------------------------
5 user calls
0 physical total bytes read
physical write 0 total bytes
0 3 spare statistics
0 commit failures of drain plug: can not pin
Extension of TBS 0: extended bytes
0 total number of times SMON post
SMON 0 posted for undo segment recovery
SMON 0 posted to drop the temp segment
prealloc segment 0 tasks
1 rows processed

9f9cf8b7-e5bc-4AAF-B369-b189dadb9d77 wrote:

Thanks for the reply

due to the second line of the execution plan. INDEX FULL SCAN PROSHIVA1. PK_LE_CLE (cost = card 175 = 284 K bytes = 1 M).

This sql takes 2 seconds. and if I remove any OF the sql condition. There are only 200 ms.

This is a typical problem optimizer - IN / associate EXISTS OR does work well in many cases. Most likely, if you simply specify the IN clause, the optimizer will unnest subquery, which could be much faster in this case.

Furthermore, the optimizer has already done a good job in eliminating unnecessary outer joins, there is no mention of CONTEXT or F_DOC in the source line of the FILTER operator. He even eliminated the SEPARATE, most likely because he knows that LETTER. LE_IDENT is unique.

Think of what the database has to do with your request - need to find matches which have the mentioned ID or who have a match in the specified list as subquery. So without more clever query processing, it must pass the primary key index set and check, for each line, if it is a match in the IN subquery - that's exactly what makes the FILTER operator, it executes the LOOP IMBRIQUEE join that represents the IN clause for each row returned by the full index scan.

Ideally, this should be transformed by using a transformation of CONCATENATION, where this query is actually split in two: part of the research for the mentioned ID and the other party responsible for looking for matches with subqueries and this making, ensuring that the two branches do not result in duplicate (since a line could satisfy both conditions).

You can try an explicit indication of USE_CONCAT for the query, but I doubt that the optimizer will do it automatically.

So if it does not, you could do the same thing as a manual rewrite:

SELECT LETTER0_. LE_IDENT AS col_0_0_

THE LETTER LETTER0_

WHERE LETTER0_. LE_IDENT = 2525432

UNION ALL

SELECT LETTER0_. LE_IDENT AS col_0_0_

THE LETTER LETTER0_

WHERE LETTER0_. LE_IDENT IN

(SELECT LETTER3_. LE_IDENT

THE LETTER LETTER3_, CONTEXT CONTEXT4_

WHERE LETTER3_. LE_PTRCTXID = CONTEXT4_. CTX_IDENT

AND CONTEXT4_. CTX_PTRPOLID = 400728434)

AND LNNVL (LETTER0_. LE_IDENT = 2525432);

The LNNVL is the bit that filter potential duplicates and which would be automatically generated by the transformation of the CONCATENATION.

Randolf

between the operator for VARCHAR values
Hello

I'm trying to compare a value varchar between two varchar values that does not work.

for example in my table there are two columns.

FROMpcode (column1)
*****************
L6P 0 TO 1
L6A 0 TO 1

TOpcode (column2)
****************
L7E 5 S 1
L6A 4R1

the value I want to compare for between FROMpcode and TOpcode is L6S 6B 7. This is the query. This is comparison of Canadian postal code.

Select * from mytablename where L6S 6B 7 between FROMpcode and TOpcode

I can't convert FROMpcode, TOpcode in numbers because they are alphanumeric data.

Thanks for your help.

Techie_nas
Hello
[email protected] wrote:
This is the create table script.
```
CREATE TABLE APPS.MYTABLENAME
(
FROM_POSTALCODE  VARCHAR2(7 BYTE),
TO_POSTALCODE    VARCHAR2(7 BYTE)
)
```
and here is the sql insert code.
```
insert into mytablename values('L0N 1A0','L7K 2P9');
insert into mytablename values('L0N 1B0','L7K 1E3');
insert into mytablename values('L6P 0A1','L7E 5S1');
insert into mytablename values('L0N 1E0','L7K 2N5');
insert into mytablename values('L0N 1C0','L7K 3L3');
insert into mytablename values('L0P 1C0','L7C 3M3');
insert into mytablename values('L0N 1K0','L7C 3M1');
insert into mytablename values('L0N 1P0','L7K 0H5');
insert into mytablename values('L0P 1N0','L7K 1N6');
```
and when I run the sql code
```
select * from mytablename where 'L6S 6B7' between from_postalcode   and to_postalcode
```
instead of only from the third row, I see all 9 lines in the results.
Why you should see only the third row? 'L6S 6B 7' is really between from_postalcode and to_postalcode of the 9 rows. Take the first row, for example:
```
insert into mytablename values('L0N 1A0','L7K 2P9');
```
'L6S 6B 7' comes after "L0N 1 to 0" in the sort order, because "L6" comes after "L0".
"L6S 6B 7" comes before "L7K 2 p 9' sort order, because"L6"comes before"L7"."

Maybe you don't really want the BETWEEN operator at all.
Explain why you want the third line and not all the others and someone will help you code.

TCP (EXAM QUESTION SOMEONE PLEASE CHECK).

Design a TCP server to provide service on port 50601 review services. The server expect to read a message of N bytes with the following structure:

Byte 0: length (u8)

1:command (u8) bytes

2... byte (N - 1) byte: bytes of data (u8)

The first byte represents the message length (N).

The second byte is the command byte.

The remaining bytes are data bytes.i.e a sequence of codes representative u8 levied a 8bits analog digital converter.

The server is as follows

1 if the command byte is the code hex 0xAA, built server a waveform to convert the table of samples U8 (data bytes) to double (dbl) and scale to represent the voltage levels between 0v and 1 v.Assume for the waveform t0 present and dt = 1ms .the server plots samples and record the wavform to the file samples.txt.and send the RECORDED DATA to the customer response

2. If the 1st byte is equal to the hexadecimal code 0xBB server builds, a waveform to convert the table of samples u8 (DATA BYTES) IN double (LDM) and sacling to represent the voltage level between 0v and 1v. THE SERVER calculates the maximum and the minimm and the avarage of samples received, show the result to the user in the fromt Panel.

3. whenever a connection is closed, the server records the date, the time, the ip address of the remote client and the byte received (on an entitled server log text file)

4. any error, the server jst responds the ERROR message or REQUEST MALFORMED and abandons the connection.

Threshold values

Hi all

If I have a sin-wave captured from an oscilloscope labview went from zero to 10 seconds, how can I do to make labview will tell me all the time when values is exactly 0?

I have explored the peak of waveform detection.vi, but do not get back useful. What is the good vi? If so, how can I do return useful data?

If this is not the case, can someone point me to the correct vi?

Thank you

From table Y of the waveform. Run it through a loop containing a = 0? comparison. Outputs true mark the presence of zeros.

However, to compare numbers floating point zero (or any other value) is not a good idea because of the resolution finished in the binary representation of numbers in the computer. It is better to compare them to a small chain around the desired value (for example, zero). You can use the stove and Coerce fucntion for this. A constant predifined called 'Epsilon Machine' represents the smallest value between the adjacent numbers on your computer. It might be appropriate to use a value from the size of a least significant bit on your oscilloscope because that represets the error of quantization in your process of tracer.

Another way to find zero crossings is to locate points in the waveform where the adjacent elements in the array have opposite signs (if no items near the zero Lorraine are exactly equal to zero).

Lynn

Error of comparison while trying to round like Excel

I have two different but related issues. First: my LabVIEW application is not passing validation of my client because the results in LabVIEW are not exactly the same as those that my customer buy when using MS Excel. The problem is with rounding: LabVIEW and Excel round numbers differently and (unfortunately) I have to round up the numbers in the way that Excel.

Because I need to round up after the comma, I started using a beautiful VI I found here at ni.com called 'DecimalRoundingLV8.5vi'. However, due to the difference between LabVIEW and Excel, I can't use this VI as it is. For example, rounded to the third place after the comma:

The number to round	LABVIEW	EXCEL
0.0045	0.0040	0,0050

So, my first question is this one, I need to round like Excel... However, the solution I implemented raised an odd question, and I don't know if I see a bug in LabVIEW.

I changed the decimal rounded VI. Here is a picture of the code and I also enclose it:

First of all, if the number is negative I change into a positive for rounding. In the end, I return the sign.

Like the original VI, I multiply the number to round up times 10 ^ x, where x is the place after the decimal point, I would like to turn to, I'm rounding and then dividing by 10 ^ x.

However, I also multiply the number of round 10 ^(x+1) time and divide the result by 10 to get the unit as the reminder and to evaluate this number. If the number is less than 5, I tour as usual; If not, round towards + infinity.

So far, so good and everything seems to be fantastic. But when I tested this code I found the following bizarre scenario. For example, rounded to the third place after the comma:

The number to round	LABVIEW	EXCEL
0.0855	0.0860	0.0860
0.0856	0.0860	0.0860
0,0857	0.0860	0.0860
0.0858	0.0860	0.0860
0.0859	0.0860	0.0860
0.0860	0.0860	0.0860
0.0861	0.0860	0.0860
0.0862	0.0860	0.0860
0.0863	0.0860	0.0860
0.0864	0.0860	0.0860
0,0865	0.0860	0.0870
0,0866	0.0870	0.0870
0,0867	0.0870	0.0870
0,0868	0.0870	0.0870
0.0869	0.0870	0.0870
0.0870	0.0870	0.0870
0.0871	0.0870	0.0870
0.0872	0.0870	0.0870
0.0873	0.0870	0.0870
0,0874	0.0870	0.0870
0,0875	0.0880	0.0880

Note When the flare 0,0865. LabVIEW is wrong! However, LabVIEW was not wrong for 0.0855 or 0,0875. When I ran the code using the highlight feature, it turns out that the problem was the comparison function. It is said literally than 5<5 is="">.

I tested in LabVIEW 8.2 and LabVIEW 12. I use Windows XP SP3.

These numbers are not the only cases with this weird behavior. Other numbers are 0.1425, 0.1725 0.1745 and more. I don't see a drawing (or a reason!)

Can someone please test my code and report if you met the same behavior?

Enrique,

It is a fundamental issue with the help of the binary representation over for numbers. Event that you post and think that numbers like decimal representations, the computer stores in a binary format. As 0.0045 or 0.004 number can be represented in binary format used by LabVIEW. Place a digital control on a new VI. Set the display format to show ~ 20 significant digits. Type in 0.004 or 0.0045 hit and hit enter.

0.0045-> 0.0044999999999999996600

The correct rounding for this value is 0.004. Of course typing 0.004 gives 0.004000000000000000080.

I don't have Excel so I don't know what it does, but it will have the same problem with approximate representations of numbers.

There are a lot of posts on the Forums about number representation.

In addition, the reason that the exact equality comparisons on the non-entier data types should be avoided or used with caution.

Lynn

Definition of tables in MathScript

I noticed a problem when using tables that have been defined using the MathScript.

If I enter A = 0.1:0.1:3 and then I get A = 0.1, 0.2, 0.3... all the way up to and including 3.

However, if I get a value greater final, say that a = 0.1:0.1:10 then the table goes up to 9.9.

Is there a reason for this deliberate or is it just some kind of bug?

James

James,

I have not checked this with Mathscript, but it is likely that what you see is the common result of the representation of numbers in binary. Values such as 0.1 infinitely repeating fractions in binary. So when you are 100 of them, the error accumulated can be sufficient to cause the effect that you saw.

Lynn

Range of channels as a box element is not included

I used the next bit of code to translate certain characters in the string into a Base36 but I discovered the element box with a range of chain is not included. For example, the following code executes the default case for a character "Z". Why is the range element string 'A'... "' Z ' not understood his last item, but a beach digital 1.10 would be? Is this a bug?

The help of LV:

For each case, use the labeling tool to enter a single value or lists and ranges of values in the tag selector at the top of the structure of the business case. For lists, use commas to separate values. For digital beaches, specify a range as 10.20, which means that all the numbers from 10 to 20 inclusively. You can also use beaches open to all. For example... 100 represents all numbers the diameter is equal to or less than 100 and 100... represents all numbers is greater than or equal to 100. For strings varies, a range a... c includes all channels starting with a or b, but not c. A range of one... c, c understands the value of end of c.

Edit: A totally separate debate is if this is the desired behavior. I tend to say no, but I'm still curious why this behavior was chosen in the first place.

for the bios HDD test what is failure id: 9GE399-559609-XD6U3G-60R103 average?

My computer laptop girls crashed after watching a movie she downloaded from the internet, the screen only I get is launching repair of windows 7 and windows boot screen 7. If I go to repair screen about half an hour later I get a blue screen, and if I go to the windows start screen I get a black screen. I tried deleting antivirus programs but no avail, any suggestions?

Duane

Hello

This is a code generated by the "F2" diagonistics integrated. In this case, this means that the HARD drive has gone wrong and needs to be replaced.

If you see a failure code after the full system diagnostic tests, write it down and contact HP support. Otherwise, the agent may ask you to go through the process of diagnostic test again to get the failure code.

The failure HP code contains four fields of six characters each, such as XXXXXX-XXXXXX-XXXXXX-XXXXXX, where X is an alphanumeric character.

Have a failure code does not mean that your computer is still under warranty. The date of start of guarantee on the computer determines if it is still under warranty. The agent can help you with this when you contact HP.

The BIOS displays error codes and messages. The error code consists of two parts. The first byte represents the field replaceable unit (FRU), and the second byte represents the test that failed. If you receive an error code, contact HP with the help error Code